I am working on a new project and I have just launched a new landing page to get feedback and allow anyone to register their email if they want to be notified when it goes live.
The website is available at https://test-track.io.
Test Track is to help developers and testing teams to manage their test plans for their various projects.
Automated tests can only get you so far, and there should be a set of tests that projects undergo to ensure functionality still works as expected and that the UX is also as expected.
For my own projects and in my full time job, we manage these tests in a giant spreadsheet detailing what it is we're trying to test, what we're expecting to happen, and if it fails, why did it fail so the development team can then fix it.
Some test steps can require complicated steps to complete or confirm that has worked, and if a test fails, it can be lengthy to explain and sometimes screenshots can help, but trying to do this is in a spreadsheet is cumbersome and easily gets managed - even worse if multiple people are working on it at the same time.
This is where Test Track comes in. You create a project and a project can have 1 or more test plans. A test plan is testing a particular part of a project, such as you might have a test plan focussed towards the main web app, another for the mobile app, and another for the backend systems.
A test plan consists of multiple different tests that should be completed. The test step, can have detailed formatted text using markdown to provide nicely laid out and formatted description of how to complete the test.
Each test plan can be triggered to perform a test run through where each step is then provided for the testing team to complete and easily mark tests as passed or failed. They get a nice formatted view of the steps if provide due to it being a more complex test to complete, and should a test fail, they themselves can provide nicely laid and out and formatted description along with screenshots to describe why the test failed.
This can then allow the development team to easily identify the problem, issue a fix and then they can mark the test for retest so the testing team know they can re-attempt the test.
Each test plan can be triggered to perform a run through, so a run through can be performed each time you need to perform a regression test on a new release.
You can check out the landing page at https://test-track.io. Any feedback greatly appreciated.
Hello Chris,
I shared some thoughts below:
Hero
Screenshots
Thanks for Registering
Pricing
This is just a quick review.
Good luck with your new project!
Hi Furkan, Sorry for the delay, trying to juggle multiple things and failing miserably :).
Thanks for the feedback - the page will be changing slightly as hoping to release by end of this week, if all goes to plan, but regarding screenshot, not sure what I can do about that, what do you mean about using browser canvas instead?