Changes between Version 14 and Version 15 of HowtoBugBuster

Timestamp:

Oct 12, 2019, 9:11:37 AM (5 years ago)

Author:

Thanatermesis

Comment:

--

HowtoBugBuster

@@ -11 +11 @@
 If you have programming knowledge it can be very helpful so on that way you know ''what common things could happen''
 
-First of all, trying to just launch the application to see if does not segfaults doesn't give anything useful, in short this is exactly what the developer does in every modification of the code, the task of a beta-tester is not to see if it works but to ''see if it can fail'', in short, it is like a challenge trying to find any possible problem, and yes, it is something '''good''' if you find any.
+First of all, trying to just launch the application to see if does not segfaults doesn't give anything useful, it is like a challenge trying to find **how** it can fail.
 
-There is a good numbers of ways to catch bugs, so let me show you some of the ways that I already know:
+But there's some techniques you can use to find these hidden bugs, so let me show you some tips:
 
 === Environment ===
-Not everybody works in the same environment or like the '''same options''', so if the developer works with the feature of application ''A'', but he never uses ''B'', it is very possible that there will be more bugs in "B" than in "A", in the same way, by trying ''not very interesting options'' you will have the same results
+Not everybody works in the same environment or using the '''same options''', so if the developer works with the feature of application ''A'', but he never uses ''B'', it is very possible that there will be more bugs in "B" than in "A", in the same way, by trying ''not very interesting options'' you will have the same results
 
-Try to imaginate how many different environments and different ways to work can exist, for example if you are beta-testing enlightenemnt 17, and you want to see if some window minimizes correctly, think about all the possibilities, you can do it by using the mouse to click the minimize button, or you can also press ''ctrl + alt + i'' on the keyboard to do the same thing, also think in other things related to minimizing an application, for example engage or taskbar can trigger the minimize too
+Try to imagine how many different environments and different ways to work can exist, for example if you are beta-testing Enlightenment 17, and you want to see if some window minimizes correctly, think about all the possibilities, you can do it by using the mouse to click the minimize button, or you can also press ''ctrl + alt + i'' on the keyboard to do the same thing, also think in other things related to minimizing an application, for example engage or taskbar can trigger the minimization too.
+
 
 === Unimaginable Possibilities ===
-Are you creative ? you need to be... think about it, in the previous example we have learnt different ways to trigger the same thing, but all the possibilities are not listed here, you need to be creative (or at least get familiarized with the application/code) to imagine how much different things can happen, for example:
+Are you creative ? you need to be... think about it, in the previous example we have seen different ways to trigger the same thing, but all the possibilities are not listed here, you need to be creative (or at least get familiarized with the application/code) to imagine how much different things can happen, for example:
  * can the window be minimized when is in maximized mode ?
  * if another window is on top of another one, we can still minimize it ?
@@ -30 +31 @@
 The previous list is just an example and you can find them useful or not to test, it all depends on you, but basically the important thing is to try everything that comes to your head that makes sense.
 
-''Expect the unexpectable'' 
+'''Expect the unexpectable'''
 [[Image(http://i.imgur.com/43sf9NL.gif)]]