Test Category
Description
Common Tools
Frontend unit test
A frontend unit test focuses on testing the userSelenium
interface. The objective is to ensure that each
user interface reacts to users' actions and
produces the output to the users as expected.
Code Quality: PMD, CheckStyle,
Continuous build and The application code base should be built on
CodePro Analytix
code quality test
a regular basis to ensure that the code quality
Test Coverage: Cobertura
complies with the standard (e.g., comments
Build Tool: Gradle, Maven, Sonar
were all in place, no empty exception catch
Continuous Build: Hudson,
block, and so on). Also, test coverage should
Jenkins
be as high as possible to ensure that all
developed lines of codes are tested.
IBM Rational Systems Tester
System integration test The system integration test verifies the
accuracy of the communication among all
programs in the new system and between the
new system and all of the external interfaces.
The integration test must also prove that the
new system performs according to the
functional specifications and functions
effectively in the operating environment
without adversely affecting other systems.
IBM Rational Functional Tester,
Functional test
Use cases and business rules are tested by
functional tests. The goals of these tests are to HP Quick Test Professional
verify that inputs are accepted properly and
outputs are generated properly, where
"properly" means in accordance both with the
use case specifications and with the business
rules. This is black-box testing by interacting
with the application via the GUI and analyzing
the results.
Apache JMeter, HP LoadRunner
System quality test
The system quality test is to ensure that the
developed application meets those
nonfunctional requirements. Most of the
time, this tests the performance of the
application to ensure that the target
requirements for concurrent users of the
system and workload are met. Other
nonfunctional requirements include security,
high availability features, and so on.
Search WWH :
