DEV Community: Kritika Yadav

Getting Restarted With Software Testing: Part 3

Kritika Yadav — Fri, 02 Jan 2026 12:57:21 +0000

This is Part 3 of our Software Testing series.
If you haven’t read Part 2 yet, you can read it here:
https://dev.to/software_ltesting_blog/getting-restarted-with-software-testing-part-2-3oc2

"Test Scenarios vs Test Cases: What’s the difference and why does it matter?"

Test scenarios is what to be tested and testcases is how to be tested.

1. Test Scenarios

A test scenario is a high-level description of what needs to be tested. It represents a real-world use case or business flow of the application.
For example: We have a web application.

Test Scenario:

Verify user login functionality

From this single scenario, multiple test cases can be derived:

2. Test Cases

Writing test scenarios in detail or step by step process to perform and validate the functionality of the software.

Key Components of a Test Case:-

Test Case ID:
Unique identifier for the test case.
Example: TC001
Test Description / Title:
Short description of what is being tested.
Example: “Verify login functionality with valid credentials.”
Preconditions:
Conditions that must be met before executing the test case.
Example: “User must be registered in the system.”
Test Steps:
Step-by-step instructions to execute the test.
Example:
Open the login page
Enter valid username and password
Click on login button
Test Data:
Input data required for the test.
Example: username = user1, password = Pass@123
Expected Result:
What the system should do after executing the steps.
Example: “User should be redirected to the dashboard.”
Actual Result (filled after execution):
What actually happened when the test was executed.
Status: Pass-Fail
Indicates if the test case passed or failed.
Remarks: Comments (optional)
Any additional information, bugs, or observations.

Positive vs Negative Test Cases: What’s the difference and why are both needed?

1. Positive Testcases

A positive test case is a test scenario where the input is valid, and the system is expected to behave as intended. The goal of positive testing is to ensure that the software works correctly when used as expected.

Positive Test Case Example:
Test Case: Verify user login with valid credentials.

Test Steps:
1. Open the login page.
2. Enter a valid username (e.g., validuser).
3. Enter the correct password (e.g., validpassword123).
4. Click the login button.
Expected Outcome:
- The user is successfully logged in and redirected to the homepage/dashboard.

2. Negative Testcases

A negative test case is a test scenario where the input is invalid, and the system is expected to handle the error or reject the input gracefully. The goal of negative testing is to verify that the software can handle unexpected or incorrect input without crashing and that it provides appropriate error messages or feedback.

Negative Test Case Example:
Test Case: Verify user login with invalid credentials.

Test Steps:
1. Open the login page.
2. Enter an invalid username (e.g., invaliduser).
3. Enter an incorrect password (e.g., wrongpassword).
4. Click the login button.
Expected Outcome:
- The system should display an error message, such as "Invalid username or password."
- The user is not logged in and remains on the login page.

What is bug in a software testing ?

Bug represent the flaw or deviation in the software application that causes it to produce incorrect or unexpected results or to behave in ways that it was not designed to.

Example 1: UI Bug (User Interface)

Description: The text on a button in an e-commerce website is not aligned properly.

Expected behavior: The text should be centered on the button.
Actual behavior: The text is pushed to the left side of the button.

Example 2: Functional Bug (Login Issue)

Description: Users cannot log in even though they enter the correct credentials.

Expected behavior: After entering correct credentials, users should be able to log in and be redirected to the homepage.
Actual behavior: After submitting valid credentials, the user is shown an error message saying "Invalid username or password."

Example 3: Performance Bug (Slow Loading)

Description: The webpage takes more than 30 seconds to load a list of products.

Expected behavior: The product page should load within 5 seconds.
Actual behavior: The product page takes a lot longer to load (more than 30 seconds).

What is a bug life cycle ?

It involves several stages where the bug is tracked, managed, and resolved, ensuring that it is fixed in the software before release.

Stages of bug life cycle:-

1. New: A bug has been identified but is not yet analyzed.
2. Assigned: A developer or team has been assigned to fix the bug.
3. Open: The bug is being worked on.
4. Fixed: The issue has been fixed by the development team.
5. Retest: The testing team verifies if the fix resolves the issue.
6. Closed: The bug is confirmed fixed, and the issue is resolved.
7. Reopened: If the issue is not fixed after the first attempt, it is reopened for further investigation.

Define bug statuses in a software testing

In software testing, bug (defect) statuses show the current state of a bug in its life cycle—from discovery to closure.

Common Bug Statuses:-

1. New

Find the defect for the first time.
Not yet reviewed by the development team.

2. Open

Bug has been reviewed and accepted.
Assigned to a developer for fixing.

3. Assigned

Bug is specifically assigned to a developer.
Bug is specifically assigned to a developer.

4. In Progress

Developer is actively working on fixing the bug.

5. Fixed

Bug has been resolved by the developer.
Code changes completed and ready for testing.

6. Pending Retest

Fix is deployed to the test environment.
Waiting for tester verification.

7. Retest

Tester is re-executing test cases to verify the fix.

8. Verified
-Tester confirms the bug is fixed successfully.

9. Closed
-Bug is fixed and no further action is required.

Rejection / Alternate Statuses:-

1. Rejected

Bug is not valid (works as designed or not reproducible).

2. Duplicate

Bug already exists in the system.

3. Deferred

Bug fix is postponed to a future release.

4. Not a Bug

Reported issue is expected system behavior.

5. Cannot Reproduce

Developer or tester cannot reproduce the issue.

Special / Advanced Statuses:-
1. Reopened

Bug reappears after being marked fixed or closed.

2. On Hold

Work paused due to dependency or missing information.

3. Won’t Fix

Bug acknowledged but will not be fixed due to low impact.

What is bug severity in a software testing ?

Severity indicates the impact of the defects on any software application. It measures how serious the defect is from a technical point of view.

Bug Severity Levels:-
1. Critical / Blocker

System crashes or becomes unusable
Testing cannot continue
Example:
- Application crashes on launch
- Server down

2. Major / High

Major functionality is broken
No workaround available
Example:
- Login not working
- Payment processing fails

3. Medium / Moderate

Partial functionality issue
Workaround exists
Example:
- Search works but filters fail

4. Low/Minor

Minor issue with minimal impact
Cosmetic or UI issues
Example:
- Button misalignment
- Font inconsistency

What is bug priority in a software testing?

Defect priority indicates how urgently a defect needs to be fixed. It helps the team decide which defects should be addressed first, based on business impact and timelines.

** Bug Priority Levels:-**
1. High Priority

Must be fixed immediately
Affects critical business functionality Example:
- Payment button not working
- App crashes during checkout

2. Medium Priority

Should be fixed, but not immediately
Core functionality works with workarounds
Example: -Profile update works but shows a warning message

3. Low Priority

Can be fixed later
Minor impact on user experience
Example: -UI alignment issue

Define roles and responsibilities of a software tester

A software tester is responsible for making sure a software product works correctly, meets requirements, and it is free of defects.

Roles of a Software Tester:-

1. Quality Assurance Role
Ensures the software meets quality standards and user expectations.
2. Defect Identifier
Finds bugs, errors, and missing features in the software.
3. Requirement Validator
Checks whether the software matches the given requirements and specifications.
4. User Advocate
Thinks from the end-user’s point of view to ensure good usability and functionality.
5. Team Collaborator
Works closely with developers, designers, and managers to improve the product.

Responsibilities of a Software Tester:-

1. Understanding Requirements
Study software requirements, designs, and use cases carefully.

2. Test Planning
Create test plans and decide what, how, and when to test.

3. Test Case Design
Write test cases and test scenarios based on requirements.

4. Test Execution
Run manual or automated tests to check software behavior.

5. Defect Reporting
Identify, document, and report bugs clearly using defect tracking tools.

6. Regression Testing
Re-test the software after fixes to ensure new changes don’t break existing features.

7. Performance and Security Testing
Check speed, stability, and basic security aspects (when required).

8. Test Documentation
Maintain test cases, test reports, and test results.

9. Automation (if applicable)
Develop and maintain automated test scripts.

10. Continuous Improvement
Suggest improvements in testing processes and product quality.

Conclusion

From understanding SDLC/STLC and testing types to identifying defects, software testing ensures every product is reliable and user-friendly. Testers play a crucial role in maintaining quality and bridging the gap between development and users. In the end, effective testing is the key to delivering software that truly works.

Getting Restarted With Software Testing: Part 2

Kritika Yadav — Fri, 26 Dec 2025 11:53:14 +0000

This is Part 2 of our Software Testing series.
If you haven’t read Part 1 yet, you can read it here:
https://dev.to/software_testing_blog/getting-started-with-manual-testing-what-ive-learned-as-a-beginner-704

Define different types of testing

We follow different types of testing approach to deliver high quality product to the customer which will be free from any bugs or defects. And it is classified into functional testing and non-functional testing.

Functional Testing

Functional testing talks about the behavior of the application and how the features should work in the application. It is categorized into different types.

Smoke Testing
Sanity Testing
Regression Testing
Retesting Testing
Ad-hoc Testing
Exploratory Testing
User Interface Testing(UI)
End To End Testing

1. Smoke Testing

Smoke testing is performed by developer and the QA team and it is used to check the basic functionalities of the software after every release. Smoke testing is done on initial builds to check whether application is stable or not.
For example: User install a new version of a food delivery app.
User quickly check:
-App installs successfully
-App opens
-Login works
-Home screen loads
-User don’t place an order yet.
-If the app crashes on launch → testing stops
-If basics work → build is accepted
-User don't check main functionality user will only look for basic functionality here this is a smoke testing.

2. Sanity Testing

Sanity testing is only done by QA members and it is used to check the main functionality of the software once the software builds gets stable.
For example: A bug was fixed where orders were failing at checkout.
Tester Verifies:
-Add item to cart
-Checkout works
-Payment goes through
-Order confirmation is shown
-User don’t test login, profile, or notifications.
-User will only look for fixed bugs and main functionality this is a sanity testing.

3. Regression Testing

This testing verifies there will be no impact on existing software while releasing the new builds for the given software.

For example: User has designed a piece of software where he can add/delete/modify customers.
Tester Verifies:
-Existing customers can still be viewed
-Customer details can be modified successfully
-Customers can be deleted without errors
-Search and filter functionality works
-Previously saved customer data is not affected

4. Retesting

In retesting whatever bugs will get in the previous builds that should be verify in the next build that is called retesting.
For example, in a cab booking app, users were not able to see the confirmation message after booking a ride.

The developers fixed the issue in the latest build. During retesting, the QA team verifies that:
-After booking a cab, the confirmation message is displayed correctly
-The message shows accurate ride details (pickup, drop, fare)
-No new issues are introduced in the booking process
-This ensures that the previously reported bug is completely resolved in the new build.

5. Ad-hoc Testing

Ad-hoc testing will be done without having any requirement or test design. Tester will randomly test the application.

For example: We have a web shop application.
Tester will randomly test:-
-Logs in with valid and invalid credentials
-Adds random products to the cart
-Refreshes the page during checkout
-Uses browser back and forward buttons

6. Exploratory Testing

In exploratory testing tester will explore the entire application. And identify all the possible scenarios and document it and use it for testing.

For example: We have online shopping application.
Tester verifies:
-Browses product categories
-Searches products using different keywords
-Adds multiple products to the cart
-Applies filters and sorting options
-Proceeds to checkout and observes validations

7. User Interface Testing

User Interface testing test the basic functionalities of the software.
For example: Font size, Font color, Spell Mistakes, Buttons and alignment issues.

8. End To End Testing

Testing the overall functionalities of the software including the data integration among all the module is called end to end testing.

For example: E-Commerce Mobile App
-Tester will verify placing and tracking order:
-User browses products and adds items to cart.
-Proceeds to checkout and applies a discount coupon.
-Selects a payment method and completes payment.
-Order confirmation is displayed, and email notification is sent.
-User tracks order delivery status in the app.
-Admin system reflects the order accurately.

Validates the entire purchase workflow, including front-end, payment, notifications, and admin tracking.

Non-Functional Testing

Non-functional testing is used to verify the different aspects of the software such as performance, speed, response and compatibility to ensure that software perform well under expected condition. And it has various types.

Performance Testing(Load, Stress, Volume)
Security Testing
Recovery Testing
Compatibility Testing
Localization & Globalization Testing

1. Performance Testing

Performance testing is used to check the speed response and stability of the software while gradually increasing and decreasing the load at the application.

Load Testing: It checks the response of the software under expected user.
For example: We have a demo web shop, and you want to check if it can handle 1000 simultaneous users browsing and placing orders without slowing down or failing.
User will send the request to the server for 1000 users and will check the response of the software whether it is working or not.
Stress Testing: It checks the response of the software beyond expected user. To find the breaking point in a software.
For example: Verify how the system performs when user load exceeds normal expectations, and check how it recovers.
User will send the request to the server for 2000-3000 users and will check the stability of the software like software is working as expected or it is failing and slowing down, once user will decrease the load at the software, application should recover and start working as expected.
Volume Testing: It checks how much data is handled by the application.
For example: Verify that the web shop can store, process, and retrieve large volumes of data without slowing down or crashing.
Test Setup:
-Insert 1 million product entries into the system.
-Create 100,000 registered users in the database.
-Simulate normal user actions:
-Search products
-View product details
-Place orders

Execution:
-Monitor response time of queries and pages
-Monitor database performance (CPU, memory, storage)
-Check if search, filters, and reports are working correctly

2. Security Testing

It ensure that user data are protected from any unauthorized access and it can not be stolen or misused by any other users.

For example: We have web shop application, If user try to login it will check credentials are valid or not.

3. Recovery Testing

It checks how fast system data is getting recover after facing any kind of failure in our system.

For example: Network Failure & Power Failure

4.Compatibility Testing

It checks the compatibility of the designed software in different devices browser and in operating system.

For example: We have an web shop application so user will check it in different browser and devices.

Browsers: Chrome, Edge, Firefox, Safari
Devices: Mobile, Laptop, Desktop, Tablet
Operating System: Android, iOS, Windows, macOS

5. Localization & Globalization

It checks our system is able to support different languages, currencies and date/time format.

For example:

The system should allow users to select different currencies: USD, EUR, INR
Language translation: English → French
Dates should adjust to regional formats (MM/DD/YYYY for USA, DD/MM/YYYY for UK).

What is test design techniques ?

This techniques is used to cover maximum test scenarios by creating less number of test cases. It is classified into different categories.

ECP[ Equivalence Class Partitioning ]
BVA[ Boundary Value Analysis ]
Decision Table
State Transition Table

1. Equivalence Class Partitioning

This techniques is used to divide the the input data into equal group called classes. Testing one value from each class is sufficient, instead of testing every possible value.

For example: We have a input data for form which accept 8-16 digit. User will divide the input into valid and invalid data and test it for a application.

Valid Input 8-16
Invalid Input Less than 8
Valid Input Less than 16
Invalid Input Greater than 16

Tester will take one input from each classes.
eg: 10, 7 , 18

2. Boundary Value Analysis

Boundary Value Analysis is used to test the data at boundary level. Because most of the time we get a error or defects at boundary level.

For example: If system accept ages from 18-60.

Min-1 = 17
Min = 18
Min+1 = 19
Max-1 = 59
Max = 60
Max+1 = 61

So boundary value for 18 and 60 is 17, 19, 59, 61.
Tester will take one boundary value for each min and max value.

3. Decision Table

Decision table is used to test and verify the software application when multiple condition are given in the designed software.

For example: We have a login page for a application.

Username Valid	Password Valid	Expected Result
Yes	Yes	Login Success
Yes	No	Error Message
No	Yes	Error Message
No	No	Error Message

4. State Transition Table

State transition table is used to test the software which provide the next data based on its previous events. It verifies whether the system behaves correctly when moving from one state to another.

For example: We have e-commerce website.

Order States:

Login
Search Product
Add to Cart
Payment
Packed
Shipped
Delivered

So, in the above example every event is depend on its previous events. User can't do it Add to Cart-----> Delivered. User has to follow each and every steps to deliver the item.
Login-->Search Product-->Add to Cart-->Payment-->Packed-->Shipped-->Delivered

Up Next

This concludes Part 2 of the Software Testing series, where we covered
important testing types and test design techniques. In Part 3, we will continue with Test Cases, Test Scenarios & Defect Management.

Getting Restarted With Software Testing: Part 1

Kritika Yadav — Thu, 18 Dec 2025 11:06:39 +0000

As a beginner I wanted to understand each and every concept of the software testing like how software build what process will be taken to design any application. Why testing is most important part of any SDLC Process. Through this blog, I am sharing my learning experiences and insights as I progress in my manual testing journey.

What is Software testing?

Software testing is nothing but one of the most important step taken in Software development life cycle to check the stability and quality of any designed software.

Why Software testing ?

Software testing is used to identify the defects in any application and it also ensure whether designed software meet all the expected requirement or not.
For example: Without Proper testing user may find some different features in a software.
-The website crashes when hundreds of users try to buy the same product simultaneously (performance issue).
-Some users are able to access other users’ accounts due to a security bug.
-Product search or checkout buttons don’t work correctly in mobile browsers (compatibility issue).

QA Vs QC

Earlier while doing the manual testing I was thinking QA and QC both work in the same way but there is huge difference between them.
Quality Assurance focus on defect prevention and it is performed by QA team. While Quality Control focus on finding the defects in any application and it is performed by tester team.

What is SDLC ?

Software development life cycle is a step by step process followed by developer and QA team to design develop test and deliver any required software.

Steps for SDLC-

What is STLC ?

Software testing life cycle is a step by step process followed by only QA team to plan design execute and report the bugs and do the defects closure of any testing activities in order to achieve the quality software.

Steps for STLC-

What is white box testing and black box testing ?

In white box testing developer will look into the internal part of the software programming. While in black box testing QA team will test the entire functionality of the software.

For example:-

White box testing: Code execution

Black box testing : No code execution

What is Levels of Testing ?

It is a combination of white box testing and black box testing. It is performed by developer and QA team to check the functionality of the software like how software behaves in different testing phases.

It is categorize into multiple phases:

Unit Testing:-

Unit testing is performed by developer to test the single module or single component of the software.

For example: We have e-commerce website.

Features in the system

Search Box
Add to cart
Order an item
Payment
Order confirm

So in the above example user will only test one component , he will login and search for the items in the search box.

Integration Testing:-

Integration testing is performed by developer to test the integrated module to check how data flow from one module to another module.

For example: We have a banking app.

Features in the system

Transfer money
Record transaction history
Get SMS/Email through notification
Check total balance

So in the above example user will check all the features to see the data flow from one module/feature to another module/feature.

System Testing:-

System testing will be perform after the completion of unit testing and integration testing. It is a black box testing performed by a testing team to check the whole functionality of the software. Before doing the system testing user should be aware of all the software requirement. And it has a various types.

Types of System testing-

GUI Testing :- Graphical user interface testing is used to check very basic functionalities like font size, font color or any alignment issues.

Functional Testing :- It is mainly focus on data base testing , error handling ,links existence, calculation, and object properties testing like size, width , length of the text box.

Non Functional Testing :- Non functional testing is used to check the speed and response of the software like performance testing, security testing, recovery testing and compatibility testing etc.

Usability Testing :- It is tested by end user to check how easily the end users are able to understand and operate the application. Preparing user manual document for the user.

UAT Testing:-

After the completion of system testing user acceptance testing will be performed by product owner or business analyst team to check whether software is ready for production or not.

Types Of UAT Testing-

Alpha Testing
Beta Testing

Alpha Testing:- Alpha testing is internal acceptance testing performed by organization team before releasing the software to the external users. And it will be done in controlled environment.

For example : We have a Banking App

Alpha Testing Scenarios:

The app is still under development.
Developers and QA testers use the app in the office.
They will test the software in test environment before releasing to the external user.

Beta Testing:- Beta testing is external acceptance testing performed by real users in real environment before the final release.

For example : We have a Banking App

Beta Testing Scenarios:

App is released to selected users
500 real users
Different devices
Different locations

Up Next

We have covered the importance of software testing and the difference between QA and QC and we have understood what is the SDLC and STLC process and levels of testing. In the up coming part we will understand software testing types and test design techniques with the real life examples.