Test case templates
Use different test case templates provided within Testiny to easily create maintainable test cases. Utilize custom fields to customize your test cases – move from spreadsheets to Testiny for more efficient test case management.
Writing manual test cases is still necessary, as automated tests are often not enough or some things are not easily testable automatically. That’s where manual test cases come in – and to make writing and maintaining them as easy as possible, you can use test case templates in order to write test cases in a structured way.
What should a test case contain?
A test case must not necessarily contain a lot of fields to be well-structured and easy-to-maintain. In Testiny, we provide the following basic fields:
- ID
To uniquely identify a test case. This is important when referencing the test case or linking to it and the title might change – it is automatically set in Testiny, so you don’t need to worry about unique IDs - Title
short description of what the test case covers - Owner
who created the test case, this field is also automatically set in Testiny - Precondition
specify any preconditions that must be fulfilled so that the test case can be executed successfully, e.g. if a certain setup is required - Steps
describe the test case step-by-step so it is easy to follow and define expected results for each step.
These standard fields should cover the basic needs of everyone who wants to write test cases in a well-structured and maintainable way. If you have more specific needs or want to map a certain process, for example, a review process or you want to flag test cases as candidates for automation, Testiny also provides the following built-in “custom fields”:
- Priority
Set your test case priority to low, medium, or high to be able to decide which test cases should be tested with a release. - Status
Mark your test case as a draft, ready for review or ready for test to implement a review process for test cases - Estimate
Estimate how long the execution of this test case takes. This allows for better planning of how long a test run takes and when it is finished for the release. - Type
Specify the type of a test case to signal the kind of test being conducted, for example, acceptance, performance, functional or usability. This can help to decide who in your team should execute a test. - Automation
Specify whether the test case is not automated, if it should be automated or if it already is automated. This also gives you the ability for better planning, for example, which test cases you want to automate in order to save resources in manual testing.
If these fields alone do not cover your specific needs, then you can also create custom fields and completely customize the test case template. This allows you to map any test case format or process to Testiny.
Workflow with Testiny
With Testiny you can then execute your test cases, split the workload among multiple testers, track the progress of the test
run and finally analyze the results. You can also filter by any test case field and optimize your test case plan.
For example, you might only want to execute test cases with a high priority or of a certain type for a specific release – this
enables you to decide what is necessary to test and helps you find an optimal trade-off between cost and quality and saves a
lot of time (and money).
Or specify whether the test case is not automated, if it should be automated or if it already is automated. This also gives you
the ability for better planning, for example, which test cases you want to automate in order to save resources in manual testing.
Can I use spreadsheets for writing my test cases?
Yes, you can – when you start out, spreadsheets might seem like a good and cheap way to write, group, filter, and sort your
test cases. However, if the number of test cases increases it gets more and more difficult to maintain your tests and track
changes. Spreadsheets also do not provide an easy-to-use rich text editor to format your test cases or to add images or
files, which are helpful or needed for execution.
Also documenting a test execution and keeping a history of your test cases is very difficult in spreadsheets and the more test
cases and the more test runs, the messier it gets. Especially, when more people want to work simultaneously on a spreadsheet
it might cause consistency problems and makes it even harder to keep an overview of who changed what and who executed which test.
That is why we would recommend not using spreadsheets, but using a dedicated test case management tool from the
beginning. It will make your life so much easier! Testiny allows you to write and maintain test cases with ease, provides
customizable test case templates to fit your needs, and makes tracking and analyzing results easy – start with Testiny.
You want to migrate from spreadsheest to a test management tool?
If you already have lots of test cases and currently maintain them in spreadsheets, you might get tired of the tedious work
of updating and tracking all changes. In Testiny, you can easily import your test cases from a spreadsheet – you might want
to have a look at an example template for importing. If the basic test case fields
provided are not enough you can also create custom fields, so that no important information is lost when importing your
tests.
Once you have imported your test cases, you can start to organize your test cases, format the test case steps or add images for
better readability and understandability. You can then easily execute the test cases and track and analyze the results to continuously
improve the quality of your software.
Learn how to migrate from CSV or Excel files to Testiny
Discover more test management features
Level up your testing game.
Start using Testiny today.
Free 14-day trial available. No credit card required.