- A/B Testing
- Agile Testing
- Continuous Integration
- Hardware Testing
- Issue Tracking
- Mobile Testing
- QA Career
- QA Training
- Software Development
- Software Releases
- Test Automation
- Test Cases
- Test Management
- Testing Documentation
- Testing Process
- Testing Tips & Guidelines
- TestLodge Tutorial
- Tools List
- Types of Software Testing
- User Stories
- UX & Usability
How to Write Test Cases for Software (with a sample)
A test case is a set of steps and results that a software product under test must meet. Here are tips on how to write test cases for software.
Types of Software Testing
Learn more about all the different types of software testing methodologies from our list below.
Agile Test Case Management - Keeping Your Test Cases Lean
Agile test case management may be straight forward, but test cases can easily become obsolete if not regularly managed, we take a look into this further.
Writing Test Cases from User Stories & Acceptance Criteria
Well thought out acceptance criteria can be a tester’s best friend. We look at how to write test cases from the user stories and acceptance criteria.
Types of Test Cases in Software Testing
There are many different types of test cases in software testing. Each type of test case helps us target software testing in a different way.
Regression testing should be done after every code change to ensure the update has not negatively affected any other part of the product.
Our overview of the software development life cycle explains how the SDLC gives structure and direction to the software development process.
In software testing, verification vs validation can be confusing. Our post explains both terms and where these test methods fit in the STLC.
Mind maps are a visual way of breaking down a big problem into more manageable units. Testing mind maps are used by QA to plan testing.
Software testers need to know software testing basics like the seven principles of testing and the STLC. This post will help you to begin.
Ahead of the full testing cycle, smoke testing ensures all the main functionality works properly before more thorough testing can commence.
The decision on when to stop testing can sometimes be a tough compromise between release schedule and providing the best product possible.
A test strategy document can inform the content of a test policy by providing general details and requirements on how testing will be done.
User Acceptance Testing (UAT) is performed after making changes to the system to ensure the addition and system work together as intended.
Our Linear test case management tool integration saves time and effort for you and your team during the software testing cycle.