Here,we discussing about non-functional system testing and these types.
- Non-Functional System Testing:
- after completion of functional system testing,test engineers concentrating on Non-functionality of an application.
- while conducting non-functional system testing,we should concentrating on expectations of customer like
- GUI Testing
- Usability Testing
- Compatibility Testing
- Hardware Configurable Testing
- Performance Testing
- Inter System Testing
- Security Testing
- Installation Testing
- Recovery Testing
- Complex Testing.
- In this testing,how professionally the application has been design,we need to check.By the time of conducting testing,we need to concentrating on below things:
a.check for alignment
b.check for the alignment of the object.
c.check whether mandatory fields got highlighted or not.
d.checking required fields and data type errors etc.
2.Usability Testing:
- during this test,concentrating on application user friendliness or not.
- it means look and feel easy to understand,short navigation comes into User friendliness.
3.Compatibility Testing:
- during this test,testing team runs software on various platforms.here platforms means operating systems.
- other system software compatibility also called as portability testing.
4.Hardware Configuration Testing:
- testing team runs software with different technology and hardware devices.
Ex: different types of input devices,output devices and supporting with different network's etc.
5.Inter System Testing:
- test team need to check one system sharing resources with another system or not OR checking inter connection between 2 software's i.e called Inter System Testing (or) End to end Testing.
6.Performance Testing:
- it means speed in processing to find a software performance.we can contact with below subsets..
a. Load testing: the execution of software under customer expected configuration or customer expected load to estimate speed in processing is called Load Testing.
b.Stress Testing: the execution of the software under customer expected configuration and more than customer expected load is called Stress Testing.
c.Spike Testing: the execution of the software under customer expected configuration and more than customer expected load,but suddenly to estimate reliability is called Spike Testing.
d.Endurance Testing: the execution of the software under customer expected configuration and more than customer expected load continuously to estimate durability(working long time) is called Endurance Testing.
7.Recovery Testing:
- it is done to check how quick and improved the system can recuperate after it has getting any type of damage or hardware malfunction etc.
- it is compulsory breakdown of the application in an assortment of conduct to validate that revival is appropriately worked.
7.Recovery Testing:
- it is done to check how quick and improved the system can recuperate after it has getting any type of damage or hardware malfunction etc.
- it is compulsory breakdown of the application in an assortment of conduct to validate that revival is appropriately worked.
No comments:
Post a Comment