Scribd
Upload
14 views4 pages

Testing Assi 2

General test case prioritization involves prioritizing test cases based on criticality, risk, and importance regardless of software version. Version-specific prioritization prioritizes test cases based on new features and changes in a particular version. Risk-based testing prioritizes test cases by assessing the likelihood and impact of potential failures and assigning test cases to relevant risks. An example uses risk-based testing to prioritize test cases for a new mobile banking feature.

Uploaded by

ashadahmedpabla
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
14 views4 pages

Testing Assi 2

General test case prioritization involves prioritizing test cases based on criticality, risk, and importance regardless of software version. Version-specific prioritization prioritizes test cases based on new features and changes in a particular version. Risk-based testing prioritizes test cases by assessing the likelihood and impact of potential failures and assigning test cases to relevant risks. An example uses risk-based testing to prioritize test cases for a new mobile banking feature.

Uploaded by

ashadahmedpabla
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Ques.

1 : Determine the difference between general test case prioritization and


version specific test case prioritization? Discuss any prioritization technique with
the help of an example.
ChatGPT
ChatGPT
General Test Case Prioritization vs. Version-Specific Test Case Prioritization:

1. General Test Case Prioritization:


 In general test case prioritization, test cases are prioritized based on their
criticality, risk, importance, and other factors regardless of the version or
release of the software.
 The prioritization criteria usually remain consistent across different versions
or releases of the software.
 The aim is to ensure that the most critical test cases are executed early in
the testing process, enabling early detection of potential defects or issues.
2. Version-Specific Test Case Prioritization:
 Version-specific test case prioritization involves prioritizing test cases
based on the specific features, changes, enhancements, or fixes introduced
in a particular version or release of the software.
 The prioritization criteria may vary from one version to another based on
the changes and priorities associated with that particular version.
 It ensures that test cases relevant to the new features or changes in the
current version receive higher priority while legacy test cases may be
deprioritized if they are less relevant to the current version.

Prioritization Technique: Risk-Based Testing

Risk-based testing is a prioritization technique that focuses on identifying and


mitigating risks associated with the software under test. It involves assessing the
likelihood and impact of potential failures or defects and prioritizing test cases
accordingly.

Example:

Consider a banking application that is introducing a new feature allowing users to


transfer funds between accounts using a mobile app. Here's how risk-based
testing can be applied:
1. Identify Risks:
 Potential risks may include:
 Security vulnerabilities in the fund transfer process.
 Compatibility issues with various mobile devices.
 Data integrity risks during the transfer process.
2. Assess Risk Impact and Likelihood:
 Security vulnerabilities could have a high impact and moderate likelihood.
 Compatibility issues may have a moderate impact and high likelihood.
 Data integrity risks could have a high impact but low likelihood.
3. Prioritize Test Cases:
 Test cases related to security vulnerabilities in the fund transfer process
would receive the highest priority due to their high impact.
 Test cases targeting compatibility issues with popular mobile devices
would be next in priority, given their high likelihood.
 Test cases addressing data integrity risks, while important, may receive
lower priority due to their lower likelihood.

By prioritizing test cases based on risk, the testing team ensures that the most
critical areas of the new feature are thoroughly tested, thereby reducing the
overall risk exposure associated with the release of the new version of the
banking application.
Anonymous
Ques. 2 : Illustrate all necessary steps of withdrawing cash from an ATM machine.
Generate test cases using class testing.
ChatGPT
ChatGPT
To illustrate the necessary steps of withdrawing cash from an ATM machine and
generate test cases using class testing, we need to consider the various
components and functionalities involved in the process. Class testing focuses on
testing individual classes or components of the system. In the case of an ATM
machine, relevant classes might include:

1. User Interface Class: Responsible for displaying options and receiving user input.
2. Account Class: Represents a user account and contains information such as
balance and account number.
3. Transaction Class: Handles transactions such as cash withdrawals, deposits, and
balance inquiries.
4. Cash Dispenser Class: Manages the dispensing of cash.

Let's outline the steps involved in withdrawing cash from an ATM machine and
then generate test cases for each class:

Steps for Withdrawing Cash from an ATM:

1. User inserts ATM card.


2. ATM machine prompts for PIN entry.
3. User enters PIN.
4. ATM machine validates the PIN.
5. ATM machine displays transaction options (e.g., Withdraw Cash, Deposit, Balance
Inquiry).
6. User selects Withdraw Cash option.
7. ATM machine prompts user to enter the amount to withdraw.
8. User enters the amount.
9. ATM machine verifies if the amount is within the withdrawal limit and available
balance.
10.If the conditions are met, the transaction is processed.
11.Cash dispenser dispenses the requested amount.
12.ATM machine updates the account balance.
13.User retrieves the cash and any printed receipt.
14.Transaction ends.

Test Cases using Class Testing:

1. User Interface Class:


 Test Case 1: Verify that the User Interface displays options correctly.
 Test Case 2: Ensure that the User Interface accepts PIN input.
 Test Case 3: Check that the User Interface displays prompts accurately.
2. Account Class:
 Test Case 4: Validate that the Account Class retrieves account balance
correctly.
 Test Case 5: Ensure that the Account Class updates balance after
withdrawal.
 Test Case 6: Check that the Account Class verifies withdrawal limits.
3. Transaction Class:
 Test Case 7: Verify that the Transaction Class processes withdrawals
accurately.
 Test Case 8: Ensure that the Transaction Class deducts the correct amount
from the account balance.
 Test Case 9: Check that the Transaction Class handles errors gracefully.
4. Cash Dispenser Class:
 Test Case 10: Validate that the Cash Dispenser Class dispenses cash
correctly.
 Test Case 11: Ensure that the Cash Dispenser Class updates cash inventory
after dispensing.
 Test Case 12: Check that the Cash Dispenser Class handles insufficient cash
scenarios.

Each test case should specify input values, expected outcomes, and any
preconditions or dependencies. By systematically testing each class's
functionality, we can ensure that the ATM machine operates reliably and securely
during cash withdrawal transactions.

You might also like