Siksha Sarovar

Siksha Sarovar (sikshasarovar.com) is a free educational web application that helps students in India learn programming and prepare for academic and competitive exams. The platform offers structured coding courses (C, C++, Python, Java, HTML, CSS, PHP, Power BI, AI, Machine Learning, Data Science), complete university curriculum notes for BCA/MCA students with previous year question papers, Class 10 and Class 12 CBSE/HBSE school notes, and dedicated preparation material for SSC, UPSC, Banking, Railway and other government exams. Browsing the site is completely free and requires no account. Users may optionally sign in with Google solely to save their learning progress, quiz scores and personal preferences across devices.

Privacy Policy | Terms of Service | Contact Siksha Sarovar | About Siksha Sarovar

v4.0.9 · PWA
Siksha Sarovar logo
Siksha Sarovar
Your Learning Universe

Siksha Sarovar is a free e-learning platform for coding courses, BCA university notes and competitive exam preparation. Optional Google sign-in saves your learning progress across devices.

Initializing knowledge base…
Compiling modules 0%

Unit 3.2: System Testing

Lesson 12 of 16 in the free Software Testing notes on Siksha Sarovar, written by Rohit Jangra.

Unit 3.2: System Testing Deep Dive

1. System Testing Overview

Definition: System Testing is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements.

  • Input: System Requirement Specification (SRS).
  • Perspective: Black Box (End-to-end functionality).
  • Environment: Must mirror the Production environment exactly.

2. Classification of System Testing

It covers "Functional" and "Non-Functional" aspects.

A. Functional System Testing

Checking the features against business requirements.

  1. Sanity Testing: A "narrow and deep" check. Performed after a bug fix to verify that the specific fix works and didn't break related modules.
  2. Smoke Testing: A "wide and shallow" check. Performed whenever a new build is received. It ensures the critical functionalities (Launch, Login) are working so the team can start deeper testing. Analogy: Plugging in a device to see if smoke comes out.
  3. Regression Testing: Re-running previous test cases on the new version. Ensuring that "Old code still works with New changes". This is the biggest candidate for Automation.

B. Non-Functional System Testing (Quality Attributes)

Checking how well the system performs.

  1. Performance Testing:
  • Load: Can it handle 10,000 concurrent users? (Expected load).
  • Stress: What happens at 20,000 users? Does it crash gracefully or corrupt data? (Breaking point).
  1. Usability Testing: Is the font readable? Is the navigation intuitive? (User Experience).
  2. Security Testing: Penetration testing, checking for SQL Injection, XSS, encryption standards.
  3. Compatibility Testing:
  • Browser: Chrome vs Firefox vs Safari.
  • OS: Windows vs Mac vs Linux.
  • Device: Mobile vs Tablet vs Desktop.
  1. Recovery Testing: If the server power is cut, does the database recover the lost transaction when power returns?