Changes between Initial Version and Version 1 of GoogleCodeInTaskTestManual


Ignore:
Timestamp:
Nov 25, 2016, 8:48:32 AM (3 years ago)
Author:
richienyhus
Comment:

Wip

Legend:

Unmodified
Added
Removed
Modified
  • GoogleCodeInTaskTestManual

    v1 v1  
     1= Manual Testing help =
     2
     3== What is Manual Testing? ==
     4When developing software, particularly larger pieces of software like say a whole operating system, you can often unintentionally add [https://simple.wikipedia.org/wiki/Software_bug 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 [https://en.wikipedia.org/wiki/Software_regression regression]. You can find regressions and software bugs in general by [https://simple.wikipedia.org/wiki/Software_testing 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.
     5
     6Because 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.
     7
     8When you or someone else is doing the testing and not the computer, this is called [https://en.wikipedia.org/wiki/Manual_testing manual testing]. The combined list of instructions and other details is called the [https://en.wikipedia.org/wiki/Test_plan 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.
     9
     10== The Test Plan ==
     11
     12A test plan is made up by a few constructs:
     13
     14* The ''user action'' is the feature that is being tested.
     15* The ''precondition'' or ''prerequisite'' is what the tester needs to do before they can properly test that particular feature.
     16* The ''expected results'' or ''expected outcome'' is what is actually ment to happen at the end of the feature test.
     17* The Steps are the step by step instructions on how to carry out the test correctly.