- 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 Releases
- 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 preconditions which a tester uses to execute a software test. 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.
Payment Gateway Testing is more than checking if an online payment is successful. Read below about the other important areas that must also be tested.
It works for me so it will work for everyone, is not the right approach when building software algorithms. Learn how to avoid creating unconscious bias.
Are you a T-shaped Software Tester or do you have what it takes to be one? Here, we list the main skills needed for you to become a T-Shaped Tester.
Sprint demos are regular meetings to inform stakeholders on progress. Inviting cross functional roles to demos creates a collaborative sharing environment.
Our post on screen reader accessibility testing helps digital product and website builders to ensure computer accessibility for the visually impaired.
Planning Poker is a highly efficient agile planning and estimating procedure that is used to help find consensus within a agile team on how long each user story will take. Due to its fun element and simplicity, it is very widely used.
Service oriented architecture testing assesses the software architecture (SOA) used for building business application using third-party services.
Adopting an inclusive design mindset at the start of every new product will help to ensure access for all abilities. Our post offers some useful pointers.
Requirement Traceability Matrix is a high-level document that keeps track of constantly updated requirements so optimum testing levels can be achieved.
There are several SDLC models available. This post assesses their different strengths and weaknesses to help you select the right one for your project.