System testing in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is system testing in software testing?

System testing is the process of testing a complete and integrated software product to verify that it meets the specified requirements.

beginner

At what stage is system testing performed?

System testing is performed after integration testing and before acceptance testing in the software development lifecycle.

beginner

Name two key goals of system testing.

1. Verify that the complete system works as expected.
2. Detect defects in the system before release.

intermediate

How is system testing different from integration testing?

Integration testing checks interactions between modules, while system testing tests the entire system as a whole.

beginner

Give an example of a type of system test.

Functional testing, performance testing, security testing, and usability testing are examples of system tests.

When is system testing usually performed?

A Before unit testing

B After integration testing

C During coding

D After acceptance testing

System testing is performed after integration testing to test the complete system.

Which of the following is NOT a focus of system testing?

A Verifying system requirements

B Testing the complete system

C Testing individual functions in isolation

D Detecting defects before release

Testing individual functions in isolation is done during unit testing, not system testing.

System testing is best described as:

A Testing the entire integrated software product

B Testing only the user interface

C Testing database queries

D Testing code modules separately

System testing tests the entire integrated software product as a whole.

Which type of testing is usually performed during system testing?

A Unit testing

B Static analysis

C Code review

D Performance testing

Performance testing is a common type of system testing.

What is the main purpose of system testing?

A To validate the complete system against requirements

B To write code

C To design the system architecture

D To deploy the software

System testing validates the complete system against its requirements.

Explain what system testing is and why it is important.

Think about testing the whole software product after all parts are combined.

Describe the difference between integration testing and system testing.

Consider the scope of what each testing type covers.

Practice

1. What is the main purpose of system testing in software development?

easy

A. To write code for new features

B. To test individual units or components separately

C. To test the complete software as a whole to verify it meets requirements

D. To deploy the software to users

Solution

1. Step 1: Understand system testing scope

   System testing tests the entire software system together, not parts separately.

2. Step 2: Compare options with system testing goal

   Only To test the complete software as a whole to verify it meets requirements describes testing the complete software to check requirements.

3. Final Answer:

   To test the complete software as a whole to verify it meets requirements -> Option C

4. Quick Check:

   System testing = whole software check [OK]

Hint: System testing checks the whole software, not parts [OK]

Common Mistakes:

• Confusing system testing with unit testing
• Thinking system testing is done before integration testing
• Believing system testing involves coding or deployment

2. Which of the following is the correct sequence of testing phases including system testing?

easy

A. Unit testing -> Integration testing -> System testing -> Acceptance testing

B. System testing -> Unit testing -> Integration testing -> Acceptance testing

C. Integration testing -> Unit testing -> System testing -> Acceptance testing

D. Acceptance testing -> System testing -> Integration testing -> Unit testing

Solution

1. Step 1: Recall testing order

   Testing starts with unit testing, then integration, then system, and finally acceptance testing.

2. Step 2: Match sequence with options

   Only Unit testing -> Integration testing -> System testing -> Acceptance testing matches the correct order.

3. Final Answer:

   Unit testing -> Integration testing -> System testing -> Acceptance testing -> Option A

4. Quick Check:

   Testing order = Unit -> Integration -> System -> Acceptance [OK]

Hint: Remember testing flows from small parts to whole system [OK]

Common Mistakes:

• Mixing up the order of integration and system testing
• Thinking system testing happens before unit testing
• Confusing acceptance testing with system testing

3. Consider this test scenario during system testing:
Test if the login page accepts valid username and password and redirects to the dashboard.
What is the expected result if the system works correctly?

medium

A. The login page shows an error message for valid credentials

B. The user is redirected to the dashboard after successful login

C. The system crashes after submitting credentials

D. The login page reloads without any message

Solution

1. Step 1: Understand the test scenario

   The test checks if valid login credentials allow access to the dashboard.

2. Step 2: Identify correct expected behavior

   On valid login, the user should be redirected to the dashboard, which is The user is redirected to the dashboard after successful login.

3. Final Answer:

   The user is redirected to the dashboard after successful login -> Option B

4. Quick Check:

   Valid login -> dashboard redirect [OK]

Hint: Valid login should lead to dashboard, not errors [OK]

Common Mistakes:

• Expecting error messages for valid inputs
• Confusing page reload with successful login
• Ignoring redirection behavior in system testing

4. During system testing, a tester finds that the software crashes when clicking the 'Submit' button on a form. What should the tester do next?

medium

A. Ignore the crash and continue testing other features

B. Restart the software and try again without reporting

C. Fix the code themselves immediately

D. Report the defect with steps to reproduce and environment details

Solution

1. Step 1: Identify correct tester action

   Testers should report defects with clear reproduction steps and environment info.

2. Step 2: Evaluate options

   Only Report the defect with steps to reproduce and environment details describes proper defect reporting. Others ignore or bypass the issue.

3. Final Answer:

   Report the defect with steps to reproduce and environment details -> Option D

4. Quick Check:

   Tester reports bugs properly [OK]

Hint: Always report bugs with clear details, never ignore [OK]

Common Mistakes:

• Ignoring critical crashes during testing
• Trying to fix code without developer role
• Not providing reproduction steps in bug reports

5. A software system has passed unit and integration tests. During system testing, it fails to handle simultaneous user logins correctly, causing data conflicts. What is the best approach to solve this issue?

hard

A. Add concurrency control mechanisms and retest the system

B. Skip system testing and release the software anyway

C. Only fix the user interface without changing backend logic

D. Reduce the number of users allowed to login simultaneously

Solution

1. Step 1: Analyze the problem cause

   Data conflicts on simultaneous logins indicate concurrency issues in backend logic.

2. Step 2: Choose appropriate fix

   Adding concurrency control (like locks or transactions) addresses the root cause and requires retesting.

3. Step 3: Evaluate other options

   Skipping testing or only fixing UI won't solve backend conflicts; limiting users is impractical.

4. Final Answer:

   Add concurrency control mechanisms and retest the system -> Option A

5. Quick Check:

   Fix concurrency bugs before release [OK]

Hint: Fix backend concurrency issues, then retest system [OK]

Common Mistakes:

• Ignoring concurrency problems during system testing
• Trying to fix only UI for backend issues
• Releasing software without fixing critical bugs