System Testing

What is System testing?
The process of performing a variety of tests on a system to explore functionality or to identify problems.
In this three types of testing levels are there.
Usability Testing
Functional Testing
Non-Functional Testing
a. Usability testing/User Interface testing (UIT): The testing team validating the user friendliness of the application like
 Easy to use : Verifying that application screen are understandable to layman level
 Look and feel : Verifying that application screens are attractable
 Speed interface: verifying that the application is having short navigations to complete the tasks.
 Verifying the spelling of each word in every screen
 Verifying the background color of each screen
 Verifying the borders of each and every section available in the application screens
 Verifying the object alignment in every screen
 Verifying the line spacing uniform between all the objects through the screens
b. Functionality testing: In this phase testers are validating the developed application functionality against SRS document(It is a block box technique)
 Validating the application behavior against SRS doc
 Input & output validation ( Taking correct type and size i/ps and providing correct o/ps)
 Backend updating coverage (The impact of front end screen operations on data tables content)
c. Non functionality testing:
 Reliability / durability: measures the application stability under load and continuation usage
 Compatibility/Portability: Validating the application functionality in customer expected platforms like different browser & Operating systems
Ex1: Performing the system testing in IE, Mozilla Firefox, Opera, Google Chrome, etc is called Browser compatibility testing
Ex2: Performing the system testing in Windows XP, Vista, W7, and Mac etc is called Operating System compatibility testing

 Configuration testing : Validating the application functionality in customer expected hardware platforms like different hard ware’s & Networks
Ex: Technology networks, Topology Networks, Printers, high end & Low configuration systems (like 32 bits, 64 bits, RAM levels, Processor levels, etc)
 Internationalization testing: Validating the developed soft ware with multi language characters
 Patch installation testing: Once any patches installed in to application servers from Microsoft updates and Norton’s security updates testers would perform the smoke level of application testing
Performance testing: Validating the developed application under different levels of load and configuration
Note1: Performance testing the part of non functionality testing which would be tested by the separate performance testing team
Note2: Load, Stress, Endurance, Data volume testing are comes under part of performance testing
 Load Testing: Performing the application testing under customer expected configuration & load
Note: Load/ Scale means that no: of concurrent users are accessing the that software
 Stress testing: Performing the application testing under customer expected configuration and peak load to breaking point of load
 Endurance /Soak testing: Performing the application testing under customer expected configuration and multiple levels of load to determine if the application can sustain the continuous expected load