System testing:-
After successfully completion of integration testing then test engineers are receiving software build from development team through common server and installing that build into test environment on that installed software build .test engineers are applying system testing to validate each and every requirement in developed software is correctly working or not as per SRS document
System testing mainly categorized into below sub tests
- Functional testing
- Non-functional testing
Functional testing:-
In functional testing test engineers are validating functional requirements in developed software as per functional requirement specification in SRS document
During functional testing test engineers are concentrate on below functional coverages on window base application and web base application
- Behavioral coverage
- Input domain coverage
- Output coverage
- Calculation coverage
- Error handling coverage
- Database coverage
- Links coverage
- URLS coverage
Behavioral coverage:-
during this coverage test engineers are validating in developed software each and every object is behaving correctly or not as per given requirement of customer in terms of enable,disable,focused....
Input domain coverage:-
during this test test engineers are validating in developed software each and every object is taking customer specified type and size of input data or not
Output coverage:-
during this test test engineers are validating in developed software each and every functionality is providing customer specified output or not w.r.t to corresponding input data
Calculation coverage:-
during this coverage test engineers are validating in developed software calculation operations are correctly working or not as per requirement of customer
Error handling coverage:-
during this coverage test engineers are validating in developed software input objects are rejecting wrong operations of users or not with corresponding error messages
Database coverage:-
during this coverage test engineers are validating completeness and correctness of database operation.
to perform database testing test engineers are receiving "database design document " from database designers this document contains entire details of corresponding database
Links coverage:-
during this coverage test engineers are validating in developed web application each and every web page is providing customer specified no. of links or not in terms of test links and image links
URL'S coverage(Uniform Resource Locator):-
during this coverage test engineers are validating in developed web pages each and every link is opening next page with specified url's or not
To perform links testing and url's testing test engineers are receiving sitemap document from web designers
this document contain each and every page links information and url's of links information
Non-functional testing:-
After successfully completion of functional testing then corresponding non functional test engineers are applying non functional testing to validate non functional requirements in developed software as per non functional requirement specification in SRS document
During non functional testing test engineers are applying below types of non functional test
- Recovery or reliability testing
- Compatibility or portability
- Hardware compatibility
- Inter system testing
- GUI or user interface testing
- Usability testing
- performance testing
- Security testing
- Parallel testing
- Installation testing
- Un installation testing
- Globalization testing
- Nationalization testing
- Benchmark testing
Recovery or reliability testing:-
during this test test engineers are validating whether developed software is recovering from abnormal situation to normal situation or not.when application going to any failure situation
Compatibility testing or portability testing:-
during this test test engineers are validating whether developed software is running or working on customer specified operating systems and browsers or not
Hardware compatibility or input devices testing:-
during this test test engineers are validating whether developed software is compatible with different companies of hardware devices or not
Inter system testing:-
during this test test engineers are validating whether developed software functionalities are coexistence with other specified software functionalities or not to perform operations and share data
GUI or User interface testing:-
during this test test engineers are validating whether our software build is providing attractive screens or not good look feel screen or not
Usability testing:-
During this test test engineers are validating whether developed software is user friendliness software or not
Performance testing:-
during this test test engineers are validating in developed software functionalities are providing response with in specified time or not as per performance specification in non functional requirement specification
It is mainly divided into two types
- Load test
- Stress test
Load test:-
during this test test engineers are validating whether developed software is supporting for customer specified load or not and each and every of functionality of software is responding with in specified time or not
Stress test:-
during this test test engineers are validating whether our developed software build is supporting more than customer expected load or not .to find out peak load or maximum capacity of load is handle by software
Security testing:-
during this test test engineers are validating whether our developed software build is providing customer specified security facilities or not, to avoid un authorized accessing secure data from data hackers
during security testing test engineers will concentrate on below coverages
- Authorization
- access control
- Encryption/Description
Authorization:-
during this coverage test engineers are validating whether developed software is giving permissions only for authorized users or valid users or not to access that software
Access control:-
during this coverage test engineers are validating whether our developed software is providing access for authorized users to use specific services
Encryption/description:-
during this coverage test engineers are validating whether developed software is converting plain text into encrypted form or not and encrypted form into plain text or not while sending data from one server to another server to secure data from data hackers
Comparative or competitive testing:-
during this test test engineers are comparing one software product features with similar types of existing products in market to find out strength and week of product
Installation testing:-
during this test test engineers are validating whether developed software is successfully installing as per developer given installation guidelines or not
Un installation testing:-
during this test test engineers are validating whether developed software is successfully un installing as per given un installation guide lines or not
Globalization(or)Internationalization:-
during this test test engineers are validating whether developed software is supporting different countries of languages ,currency date and time settings or not .the software is developed for global users
Nationalization(or)Localization:-
during this test test engineers are validating whether developed software is supporting for particular country language,currency,date and time settings or not
Benchmark testing:-
during this test test engineers are validating whether software is developed according to company standards or not
0 comments:
Post a Comment