|Version 5 (modified by 4 years ago) ( diff ),|
Manual Testing help
What is Manual Testing?
When developing software, particularly larger pieces of software like say a whole operating system, you can often unintentionally add bugs and issues when you are adding in new features. When you break a pre-existing feature that was previously working correctly, this is called a regression. You can find regressions and software bugs in general by testing the software to see what is working and what isn't. This is done by either getting the computer to do it or by doing it yourself.
Because bugs and regressions can easily slip into software, it is important to test your software before releasing it. However if you don't have a predefined plan on what to test and how to go about doing it, then you might not test everything in the same way everytime, so you are bound to mess up and release software filled with regressions and crippling bugs. It becomes even more messy if you get other people to help you test your software, as they might not know about all the features of the software or how to use it.
When you or someone else is doing the testing and not the computer, this is called manual testing. The combined list of instructions and other details is called the Test plan. By using a Test Plan you can make the testing of your application more consistent, increasing the chances of you catching regressions before it's too late.
The Test Plan
The anatomy a Test Plan
A test plan is made up by a few constructs:
- The user action is the feature that is being tested.
- The precondition or prerequisite is what the tester needs to do before they can properly test that particular feature.
- The expected results or expected outcome is what is actually ment to happen at the end of the feature test.
- The steps are the step by step instructions on how to carry out the test correctly. (Use two pipes "||" to separate each step.)
Test Plan examples
|User Action||Precondition||Expected Results||Steps|
|Dragging & dropping midi files onto MidiPlayer while playing||Put two midi files that you will test somewhere convenient, like on your desktop.||The old song stops and the new midi song is played.||Start playing the first midi file. || Drag & drop the second midi file onto the MidiPlayer window|
|Disable and re-enable the Scope||The main window is open||When disabled the midi plays successfully and the scope is not displayed, when re-enabled midi plays successfully and the scope is displayed.||Uncheck the check box marked scope || The check box is then unckecked || Click the button marked play || Stop the midi from playing || Check the scope checkbox || The checkbox is then checked || Click play|
You can download an example test plan here and simplified template for you to edit for your task. They are both CSV files (comma separated values file), which is the same format that you need to submit your work as.
They can either be opened using a spreadsheet application where you just edit the cells, or you can open it in a text editor where you have to deal the formatting yourself, but which is more powerful.
On Haiku you can download the spreadsheet application SumIt from the HaikuDepot app store and the advanced text editor application Pe is currently bundled with all copies of the Haiku operating system. On Windows you can use Microsoft Excel and Microsoft Notepad, while on Mac you can use Apple Numbers and Apple TextEdit. On Linux you can use Gnumeric or Calligra Sheets and the text editors gedit or KWrite.