Skip to main content
Home
  • Tutorials
    • Quality Assurance
    • Software Development
    • Machine Learning
    • Data Science
  • About Us
  • Contact
programsbuzz facebook programsbuzz twitter programsbuzz linkedin
  • Log in

Main navigation

  • Tutorials
    • Quality Assurance
    • Software Development
    • Machine Learning
    • Data Science
  • About Us
  • Contact

System Testing

Profile picture for user devraj
Written by devraj on 09/20/2020 - 21:45

System testing focuses on the behavior and capabilities of a whole system or product, often considering the end-to-end tasks the system can perform and the non-functional behaviors it exhibits while performing those tasks. System Testing is a level of testing that validates the complete and fully integrated software product. 

System testing often produces information that stakeholders use to make release decisions. System testing scope shall be clearly addressed in the Master and/or Level Test Plan for that test level. 

Table of Content

  1. Types of System Testing
  2. Objectives of System Testing
  3. Test Basis
  4. Test Objects
  5. Typical Defects and Failures
  6. Specific Approaches and Responsibilities
  7. Video Tutorial

1. Types of System Testing

Some commonly known types of System Testing include:

  • Usability Testing
  • Load Testing
  • Stress Testing
  • Scalability Testing
  • Regression Testing
  • Recovery Testing
  • Migration Testing
  • Security Testing

2. Objectives of System Testing

Objectives of system testing include:

  • Reducing risk
  • Verifying whether the functional and non-functional behaviors of the system are as designed and specified
  • Validating that the system is complete and will work as expected
  • Building confidence in the quality of the system as a whole. In some cases, automated system regression tests ensure that changes have not broken existing features or end-to-end capabilities.
  • Finding defects
  • Preventing defects from escaping to acceptance test levels or production
  • For certain systems, verifying data quality may also be an objective.
  • System testing may also satisfy legal or regulatory requirements or standards.

3. Test Basis

Examples of work products that can be used as a test basis for system testing include:

  • System and software requirement specifications (functional and non-functional)
  • Risk analysis reports
  • Use cases
  • Epics and user stories
  • Models of system behavior
  • State diagrams
  • System and user manuals

4. Test Objects

Typical test objects for system testing include:

  • Applications
  • Hardware/software systems
  • Operating systems
  • System under test (SUT)
  • System configuration and configuration data

5. Typical defects and failures

Examples of typical defects and failures for system testing include:

  • Incorrect calculations
  • Incorrect or unexpected system functional or non-functional behavior
  • Incorrect control and/or data flows within the system.
  • Failure to properly and completely carry out end-to-end functional tasks
  • Failure of the system to work properly in the system environment(s)
  • Failure of the system to work as described in system and user manuals

6. Specific approaches and responsibilities

  • Focus: System testing should focus on the overall, end-to-end behavior of the system as a whole. System testing should investigate both the functional and non-functional requirements of the system.  
  • Technique Used: System testing should use the most appropriate techniques for the aspect(s) of the system to be tested. For example, a decision table may be created to verify whether functional behavior is as described in business rules.
  • Who performs it: System testing is typically carried out by independent testers who rely heavily on specifications. 
  • Early involvement of testers: Defects in specifications (e.g., missing user stories, incorrectly stated business requirements, etc.) can lead to a lack of understanding of, or disagreements about, expected system behavior. Such situations can cause false positives and false negatives, which waste time and reduce defect detection effectiveness, respectively. Early involvement of testers in user story refinement or static testing activities, such as reviews, helps to reduce the incidence of such situations.
  • Test Environment: The test environment should ideally correspond to the final target or production environment possible to minimize the risk of environment-specific failures at higher levels.
Related Content
ISTQB CTFL Tutorial
Integration Testing
Acceptance Testing
  • Log in or register to post comments

Choose Your Technology

  1. Agile
  2. Apache Groovy
  3. Apache Hadoop
  4. Apache HBase
  5. Apache Spark
  6. Appium
  7. AutoIt
  8. AWS
  9. Behat
  10. Cucumber Java
  11. Cypress
  12. DBMS
  13. Drupal
  14. GitHub
  15. GitLab
  16. GoLang
  17. Gradle
  18. HTML
  19. ISTQB Foundation
  20. Java
  21. JavaScript
  22. JMeter
  23. JUnit
  24. Karate
  25. Kotlin
  26. LoadRunner
  27. matplotlib
  28. MongoDB
  29. MS SQL Server
  30. MySQL
  31. Nightwatch JS
  32. PactumJS
  33. PHP
  34. Playwright
  35. Playwright Java
  36. Playwright Python
  37. Postman
  38. Project Management
  39. Protractor
  40. PyDev
  41. Python
  42. Python NumPy
  43. Python Pandas
  44. Python Seaborn
  45. R Language
  46. REST Assured
  47. Ruby
  48. Selenide
© Copyright By iVagus Services Pvt. Ltd. 2023. All Rights Reserved.

Footer

  • Cookie Policy
  • Privacy Policy
  • Terms of Use