Concurrency
Testing: When multiple user access the same application with same
code, database records and module then what effect will show on
application. This scenario will be tested in concurrency testing. Performance
Test Engineers performed such type of testing.
Real world scenario for, software testing techniques, Big Bang Integration Testing, binary portability testing, boundary values testing, branch testing, breadth testing, compatibility testing, comparison testing,
- Compliance Testing: This testing confirms that developed application has been satisfying the policies, standard and all required certifications. This testing has been performed by the external companies.
- Condition coverage Testing: This testing covers the application for all possible conditions. It will test on the base of yes/no condition. This testing typically processed by the automation Test Engineers.
- Configuration Testing: This testing confirms the optimal and minimal configuration of software and hardware requirement. Also confirm the changes or updates made for resources such as CPU, memory and disk drives. This testing always done by performance test engineers.
- Component Testing: This testing is similar to unit testing but this is for higher lever of integration. In this testing tester will test context instead of just testing the small unit. This testing can be done by both teams either by the development team or software testing team.
- Comparison Testing: In this testing Test Engineers will compare the newly developed product/software to old version application or any other application to confirm its quality. This testing can be done any one mean either by developer or Test Engineers.
- Compatibility Testing: This software testing type will validate how an application will performs in particular environment i.e. operating system/network/software configuration/hardware configuration. Usually this testing is performed by the Test Engineers.
- Code – Driven Testing: This testing with the help of frameworks test the various section of code. This testing will ensure the developed code is giving the expected result or not. This testing conducted by the software engineers.
- Black Box Testing: This testing confirm/match the requirement of application with the developed application. In this testing tester will test the front end and its functionality of testing. Here tester needs not any type of knowledge related to internal code. This is done by the QA Teams.
- Breadth Testing: It’s a test suite which tests the all functionality but does not test the characteristics in details. This testing performed by the Test Team Engineers.
- Branch Testing: This is a type of white box testing. In this testing tester will test all branch of code at least one time. This testing can be done by the developers.
- Bottom Up Integration Testing: Bottom mean first test the units uniquely and the test integrated units and finally test all integrated units as a system testing. This will called bottom up integration testing and this testing is done by the software test engineers.
- Boundary Value Testing: This testing is based on the result of boundary values of system. A system will be tested with the help of boundary values and all results will be assumed same as the boundary values result. This testing conducted by the QA Team.
- Binary Portability Testing: This testing confirm the application is portable with binary platform or not. Testing team perform this testing.
- Big Bang Integration Testing: In this testing when all units will be ready then all will integrated at once then all system will be tested at once, So this is called big bang integration testing. Testing team performs this testing.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
Real world scenario for, software testing techniques, Big Bang Integration Testing, binary portability testing, boundary values testing, branch testing, breadth testing, compatibility testing, comparison testing,
No comments:
Post a Comment