Part - 2 Areas to be looked at when testing

Dear All,
Here iam back again with more on testing.This article is an continuation from where we left on areas to be looked at when testing. So let's start,

When testing an Application Programming Interface (API) testing

The following tasks can be automated:
1. Test-code builds
2. Test-suites execution
3. Report generation
4. Report publishing
5. Report notification
6. Periodic execution of test-suites
7. A tool for test automation should be identified very early in the project.
8. 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

When doing a Middleware Testing
• Functional testing
• Interoperability testing
• Performance testing

When doing a Database/ Backend (and database applications) 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); aspects to be tested:
• Dataset
• Numeric
• Alpha
• Numerosity
• Field size
• Data structures
• Timeouts
Accuracy/ Integrity testing (Data); aspects to be tested:
Boundary conditions testing (Data); aspects to be tested:
• Calculations - Reports
• Calculations - Backend
• Divide by zero
• Truncate
• Compatibility
• Test data
• Data consistency
Database connectivity; aspects to be tested:
• Save
• Retrieval
Database schema testing; aspects to be tested:
• Databases and devices
• Tables, Fields, Constraints, Defaults
• Keys and Indices
• Stored procedures
• Error messages
o Triggers, Update
• Triggers, Insert
• Triggers, Delete
• Schema comparisons
Security testing; aspects to be tested
• Login and User security

When doing a Web Site/ 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

• Functional Testing
Web site functional testing
Testing for completeness and consistency of web pages
• Performance Testing
Load testing of web based systems
Reliability, performance and scalability testing of web applications
Load and performance testing of web server