Changes between Version 3 and Version 4 of GoogleCodeInTaskTestAdHoc

Timestamp:

Nov 24, 2016, 5:20:24 AM (8 years ago)

Author:

richienyhus

Comment:

Add small introduction

GoogleCodeInTaskTestAdHoc

@@ -4 +4 @@
 When 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] see what is working and what isn't. This is done by either getting the computer to do it or to getting a real person to do it. However you have to either give the computer or the (person you hired to be a) bug tester lengthy step by step instructions on what they need to check and how to do it. 
+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 getting a real person to do it. However you have to either give the computer or a person (who you hired to be your bug tester) lengthy step by step instructions on what they need to check and how to do it. 
 
-Ad hoc is a [https://en.wiktionary.org/wiki/ad_hoc Latin term meaning] impromptu, spontaneous or 'on the spot' behaviour and action, thus [https://en.wikipedia.org/wiki/Ad_hoc_testing ad hoc testing] means that there is not formal plan.
+''Ad hoc'' is a [https://en.wiktionary.org/wiki/ad_hoc Latin term meaning] impromptu, spontaneous or 'on the spot' behaviour and action; therefore [https://en.wikipedia.org/wiki/Ad_hoc_testing ad hoc testing] means that there is no formal plan, that the tester creates their own plan and simply records the bugs they found and how they found them. 
 
+However there is a downside to ad hoc testing, it is pointless if the bug tester does not give instructions on how to reproduce bugs they find, otherwise developers would not be able to study them further. Plus if testers don't report what features they have tested, then developers don't know if a features is working or if it was just not tested by the bug tester.
 
 
@@ -32 +33 @@
 1. Try look on [http://alternativeto.net AlternativeTo] for alternative software on other operating systems.
 1. Have a look at the blurb and the sales pitch of other software to see what features they list.
-1. Download one two of the more popular applications on the operating system that you normally use and test their features out.
+1. Download one or two of the more popular applications on the operating system that you normally use and test their features out.
 1. Try ask users on [https://discuss.haiku-os.org/c/Development/application our forums] what type of features that would want from that type of application.