Posts Tagged Software Testing Levels

Software Testing Levels

Have you ever thought why do you need to categorize software testing into different types? What are the benefits of dividing software testing in different types? One of the main purposes of software testing is to identify defects in the software. Defects in software testing can be defined as variance from requirement or user expectation. Based on this simple definition, it is very easy to categorize defects. For example:  If system is not functioning properly, its a functional defect, If system is not performing well, its a performance defect, If system is not usable, its a usability defect, If system is not secure, its a security defect

Identify these different defects require different skill set, different techniques and different type of test cases. Testing is divided into different types to reflect, what kind of defects can be uncovered by those activities. This division also helps management in managing these activities effectively. Also, it is very rare to have someone with skills in all the types of testing and this division helps in getting proper resources for team.

Hope you understand importance of this categorization and also how important it is to have understanding of different types. This understanding will enable you to spot more defects which in turn will improve quality and make you more effective software tester.

There are many ways in which software testing can be categorized. Some of them are described as follows:

Categorization of testing based on the knowledge of system

• Black Box Testing

• White Box Testing

• Gray Box Testing

Levels of Testing is Categorization of testing based on the time it is executed in the Software Development Life Cycle

• Unit Testing

• Integration Testing

• System Testing

• User Acceptance Testing

Different types of testing can be categorized based on the purpose of testing. This can be classified further into Functional Testing and Non Functional Testing.

• Functional Testing

In functional testing, the focus of testing activities is on functional aspects of the system. In functional testing, test cases are written to check the expected output. Functional testing is normally performed in all the test phases from unit to system testing.

The following types of test activities are normally performed under Functional Testing

o Installation Testing

o Regression Testing

o Upgrade and backward compatibility testing

o Accessibility testing

o Internationalization and localization testing

o API Testing

• Non-Functional Testing

In non-functional testing, the focus of the testing activities is on non functional aspects of the system. Non functional testing is normally carried out during the System Testing phase only. The focus of non functional testing is on the behavior and user experience of the system.

o Performance, Load and Stress Testing

o Usability Testing

o Security testing

Testing can also be categorized based on how it is executed. Execution  could be in the form of verification or static analysis or it could be validation or dynamic analysis. Verification and validation can be categorized further according to how it is done.

• Verification

In very simple terms, verification is the human examination or review of the work product. There are many forms of verification which ranges from informal verification to formal verification. Verification can be used for various phases in SDLC and can be in the form of formal inspection, walkthrough or buddy-checking.

Validation

Validation or dynamic analysis is the most frequent activity that as a tester you perform. Whether you are doing black box testing, non functional testing or any type of testing, chances are that you are performing validation or dynamic analyses. Validation or dynamic analyses is associated with the execution, and could be related to the execution of test cases or testing in general. There are many ways in which testing can be executed, for example

o Manual Scripted Testing

o Exploratory Testing

o Automated Testing

o Model Based Testing

Tags: , ,

System Testing

System Testing is probably the most important phase of complete testing cycle. This phase is started after the completion of other phases like Unit, Component and Integration testing. During the System Testing phase, non functional testing also comes in to picture and performance, load, stress, scalability all these types of testing are performed in this phase.

By Definition, System Testing is conducted on the complete integrated system and on a replicated production environment. System Testing also evaluates that system compliance with specific functional and non functional requirements both.

It is very important to understand that not many test cases are written for the system testing. Test cases for the system testing are derived from the architecture/design of the system, from input of the end user and by user stories. It does not make sense to exercise extensive testing in the System Testing phase, as most of the functional defects should have been caught and corrected during earlier testing phase.

Utmost care is exercised for the defects uncovered during System Testing phase and proper impact analysis should be done before fixing the defect. Some times, if business permits defects are just documented and mentioned as the known limitation instead of fixing it.

Progress of the System Testing also instills and build confidence in the product teams as this is the first phase in which product is tested with production environment.

System testing phase also prepares team for more user centric testing i.e. User Acceptance Testing.

Entry Criteria

  • Unit, component and Integration test are complete
  • Defects identified during these test phases are resolved and closed by QE team
  • Teams have sufficient tools and resources to mimic the production environment
  • Teams have sufficient tools and resources to mimic the production environment

Exit Criteria

  • Test cases execution reports shows that functional and non functional requirements are met.
  • Defects found during the System Testing are either fixed after doing thorough impact analysis or are documented as known limitations.

Tags: ,