|
|
|
 |
 |
|
 |
|
 |
|
 |
|
 |
|
| |
 |
|
| |
 |
|
| |
 |
|
| |
 |
Technology Based Software Testing |
| |
 |
|
| |
 |
|
| |
 |
|
| |
 |
|
| |
| Products |
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
|
|
|
|
|
|
Technology Based Software Testing
GUI Testing
Communication; aspects to be tested are:
Missing information:
- Enable/ Disable toolbar buttons
- Wrong/ misleading/ confusing information
- Help text and Error messages
- Training documents
|
 |
Dialog Boxes; aspects to be tested are:
- Keyboard actions
- Mouse actions
- Canceling
- Okaying
- Default buttons
- Layout error
- Window buttons
- Sizable
- Title/ Icon
- Tab order
- Display layout
- Boundary conditions
- Sorting
- Active window
- Memory leak
Command structure:
- Menus
- Popup menus
- Command Line Parameters
- State transitions
Program rigidity:
- User options
- Control
- Output
Preferences; aspects to be tested are:
- User tailor-ability
- Visual preferences
- Localization
Usability; aspects to be tested are:
- Accessibility
- Responsiveness
- Efficiency
- Comprehensibility
- User scenarios
- Ease of use
Localization; aspects to be tested are:
- Translation
- English-only dependencies
- Cultural dependenciesv
- Unicode
- Currency
- Date/ Time
- Constants
- Dialog contingency
Application Testing
- Java Applications/.NET/ Applets
- Automated component testing
- Functional testing
- Performance testing
- Applet/ application testing
- Code coverage
- Boundary conditions testing
Application Programming Interface (API) testing
The following tasks can be automated:
- Test-code builds
- Test-suites execution
- Report generation
- Report publishing
- Report notification
- Periodic execution of test-suites
- A tool for test automation should be identified very early in the project.
- A simulator (that services the API calls) should be developed by the testing team. In the absence of this simulator, there is a dependency on a Server (not developed by the API development team).
Validating the APIs for user-friendliness:
- Meaningful names
- Concise and short names
- Number of arguments
- Easy-to-read names
Middleware testing
- Functional testing
- Interoperability testing
- Performance testing
Database/ Backend Testing
Apart from testing (verify/ validate this) the application the following needs to be considered for databases:
- Distributed Environment
- Performance
- Integration with other systems
- Security Aspects
- Description/ Sub-tasks
Boundary conditions testing (Data):
- Dataset
- Numeric
- Alpha
- Numerosity
- Field size
- Data structures
- Timeouts
Accuracy/ Integrity testing (Data):
- Calculations - Reports
- Calculations - Backend
- Divide by zero
- Truncate
- Compatibility
- Test data
- Data consistency
Database connectivity:
Database schema testing:
- Databases and devices
- Tables, Fields, Constraints, Defaults
- Keys and Indices
- Stored procedures
- Error messages
- Triggers, Update
- Triggers, Insert
- Triggers, Delete
- Schema comparisons
Security testing, aspects to be tested:
Website/ Page Testing
Link and HTML Testing :
- Detecting HTML compatibility problems
- Checking Cascading Style Sheets
- Checking link and content
- Checking HTML syntax/ Validating HTML documents
- Detecting broken/ dead links
- Web site performance analysis
Performance Testing:
- Load testing of web based systems
- Reliability, performance and scalability testing of web applications
- Load and performance testing of web server
|