Unit Testing:-
• Testing
of Individual Unit (E.g. : Function, Program, Module)
1. Also
referred to as White Box Testing
2. Typically
performed by the Developer
3. Goal
of Unit testing is to uncover defects using formal techniques like:
• Resource-behavior
(e.g. memory leaks), performance or robustness testing, as well as structural
testing
• Defects
and deviations in Date formats
• Special
requirements in input conditions (for example Text box where only numeric or
alphabets should be entered)
• Selection
based on Combo Box’s, List Box’s, Option buttons, Check Box’s
• Testing
occurs with access to the code being tested, with the support of the
development environment, such as a unit test framework or debugging tool.
4.
The testing must ensure:
• Statement
Coverage
• Condition
Coverage
• Exceptional
Conditions Coverage
5.
Tools that can be used:
•
Junit, JTest Case, Cactus, Jindent, Rational
Quantifier, Rational Purifier
System Testing:-
• Also
referred to as a special Black Box Testing
• It
is a series of different end to end tests that fully exercise the application
• Each
test verifies that system elements have been properly integrated and perform
allocated functions
• Performed
by the Tester
• Test
Environment (S / W, H / W, Data) must be as close as possible to production
• Test
Environment must be different from Development Environment
• Test
scenarios covers:
– Functional
Requirements
– Non-functional
Requirements (Performance, Recovery, Usability) – Optional
– Automated
Tools that can be used
– Functional
Test Automation – Mercury Win Runner, Rational Robot, Test Partner, QTP
– Performance
Testing – Mercury Load Runner, Rational Performance tester, VSTS, Open STA
(open source)
You may also like:
Complete Testing Material
Testing basic interview questions
No comments:
Post a Comment