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

Testing Fundamentals - Testing Types and Levels

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?

AAdd concurrency control mechanisms and retest the system

BSkip system testing and release the software anyway

COnly fix the user interface without changing backend logic

DReduce the number of users allowed to login simultaneously

Step-by-Step Solution

Solution:

Step 1: Analyze the problem cause
Data conflicts on simultaneous logins indicate concurrency issues in backend logic.
Step 2: Choose appropriate fix
Adding concurrency control (like locks or transactions) addresses the root cause and requires retesting.
Step 3: Evaluate other options
Skipping testing or only fixing UI won't solve backend conflicts; limiting users is impractical.
Final Answer:
Add concurrency control mechanisms and retest the system -> Option A
Quick Check:
Fix concurrency bugs before release [OK]

Quick Trick: 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

Master "Testing Types and Levels" in Testing Fundamentals

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Trace Try Challenge Automate Recall Frame

More Testing Fundamentals Quizzes

What is the best approach to solve this issue?

Step 1: Analyze the problem cause

Step 2: Choose appropriate fix

Step 3: Evaluate other options

Final Answer:

Quick Check:

Want More Practice?