Sunday, January 30, 2011

General scenario to test desktop application manually

General scenario to be covered to test desktop application manually:
1. Functionality test as per specs of the application
2. Usability tests.
3. Screen load/ Operation times/ Response times.
4. Fail over scenarios, mostly depend on application
5. Compatibility testing.
6. Installation, then re-installation testing.
7. Recovery testing, what if application crashes. Is data lost?
8. Print functionality.
9. Keyboard shortcuts (Hot-keys).
10. Cut/ Copy/ Paste functionality.
11. Minimize/ Maximize/ Resize.
12. Help functionality.

Monday, January 17, 2011

White box and black box testing

White box and black box testing are terms used to describe the point of view a test engineer takes when designing test cases. Black box being an external view of the test object and white box being an internal view. Software testing is partly intuitive, but largely systematic. Good testing involves much more than just running the program a few times to see whether it works. Thorough analysis of the program under test, backed by a broad knowledge of testing techniques and tools are prerequisites to systematic testing. Software Testing is the process of executing software in a controlled manner; in order to answer the question “Does this software behave as specified?” Software testing is used in association with Verification and Validation. Verification is the checking of or testing of items, including software, for conformance and consistency with an associated specification. Software testing is just one kind of verification, which also uses techniques as reviews, inspections, walk-through. Validation is the process of checking what has been specified is what the user actually wanted.

Software Testing

It is the process used to help identify the correctness, completeness, security, and quality of developed computer software. Testing is a process of technical investigation, performed on behalf of stakeholders, that is intended to reveal quality-related information about the product with respect to the context in which it is intended to operate. This includes, but is not limited to, the process of executing a program or application with the intent of finding errors. Quality is not an absolute; it is value to some person. With that in mind, testing can never completely establish the correctness of arbitrary computer software; testing furnishes a criticism or comparison that compares the state and behavior of the product against a specification. An important point is that software testing should be distinguished from the separate discipline of Software Quality Assurance (SQA), which encompasses all business process areas, not just testing.