Difference between revisions of "Bugfixing/en"

From 2value wiki 2
Jump to navigation Jump to search
(Created page with "{{languages|Bugfixing}} '''Bugfixing is letterlijk het oplossen van fouten. In praktijk betekent het echter veel meer...''' So what are those tips: 1) Understand the whole a...")
 
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
{{languages|Bugfixing}}
 
{{languages|Bugfixing}}
−
'''Bugfixing is letterlijk het oplossen van fouten. In praktijk betekent het echter veel meer...'''
+
'''Bugfixing is literally solving a problem. However bugfixing consists of a lot more...'''
  
−
So what are those tips:
+
==Bug fixing consists of==
  
−
1) Understand the whole application or module in depth before starting the testing.
+
===Communication===
 +
*Receive and understand the bug report
 +
*Ask for additional information
 +
*Give status reports
 +
*Ask circumstantial information
  
−
2) Prepare good test cases before start to testing. I mean give stress on the functional test cases which includes major risk of the application.
+
===Configure the bug finding and fixing environment===
 +
Precondition is you have your personal development environment in place.
  
−
3) Create a sufficient test data before tests, this data set include the test case conditions and also the database records if you are going to test DB related application.
+
===Find the bug===
 +
:1. Isolate the bug
 +
::which situation
 +
::which platform
 +
::using what Graphical User Interface object
 +
::which pre condition
 +
::what data input?
  
−
4) Perform repeated tests with different test environment.
+
:2. Make the bug reproducible. Show when and where a bug appears.  
  
−
5) Try to find out the result pattern and then compare your results with those patterns.
+
The bug is considered "found" in all its extent if all platforms all situations, all etc. are tested or logically excluded.
  
−
6) When you think that you have completed most of the test conditions and when you think you are tired somewhat then do some monkey testing.
+
===Fix the bug===
 +
*...or make a workaround
 +
*Document the bug and its fix
  
−
7) Use your previous test data pattern to analyse the current set of tests.
+
===Have fix the bug fix tested===
 +
Organizations and individuals that just survived a bug are quite sensitive. Test the fix before delivery.  
  
−
8) Try some standard test cases for which you found the bugs in some different application. Like if you are testing input text box try inserting some html tags as the inputs and see the output on display page.
+
===Stage the fix to acceptance and production===
 +
Have the bug fix approved.
  
−
9) Last and the best trick is try very hard to find the bug ;-) As if you are testing only to break the application!
+
==amenability==
 +
<small>From: http://www.softwaretestinghelp.com/how-to-find-a-bug-in-application-tips-and-tricks/</small>
 +
 
 +
==What actions cost time & expertise?!==
 +
In addition the activities mentioned above, we have to account for the following activities:
 +
:1) Understand the whole application or module in depth before starting the test.
 +
:2) Prepare good test cases before start to test
 +
:3) Create sufficient test data before tests, this data set include the test case conditions and also the database records if you are going to test DB related application.
 +
:4) Perform repeated tests with different test environment. Report results.
 +
:5) Try to find out the result pattern and then compare your results with those patterns.
 +
:6) Evaluate test data pattern to analyse the current set of tests. Reproduce all bug-patterns.

Latest revision as of 06:57, 11 July 2012

Language: Nederlands  • English

Bugfixing is literally solving a problem. However bugfixing consists of a lot more...

Bug fixing consists of

Communication

  • Receive and understand the bug report
  • Ask for additional information
  • Give status reports
  • Ask circumstantial information

Configure the bug finding and fixing environment

Precondition is you have your personal development environment in place.

Find the bug

1. Isolate the bug
which situation
which platform
using what Graphical User Interface object
which pre condition
what data input?
2. Make the bug reproducible. Show when and where a bug appears.

The bug is considered "found" in all its extent if all platforms all situations, all etc. are tested or logically excluded.

Fix the bug

  • ...or make a workaround
  • Document the bug and its fix

Have fix the bug fix tested

Organizations and individuals that just survived a bug are quite sensitive. Test the fix before delivery.

Stage the fix to acceptance and production

Have the bug fix approved.

amenability

From: http://www.softwaretestinghelp.com/how-to-find-a-bug-in-application-tips-and-tricks/

What actions cost time & expertise?!

In addition the activities mentioned above, we have to account for the following activities:

1) Understand the whole application or module in depth before starting the test.
2) Prepare good test cases before start to test
3) Create sufficient test data before tests, this data set include the test case conditions and also the database records if you are going to test DB related application.
4) Perform repeated tests with different test environment. Report results.
5) Try to find out the result pattern and then compare your results with those patterns.
6) Evaluate test data pattern to analyse the current set of tests. Reproduce all bug-patterns.
Retrieved from "http://wiki.2value.nl/index.php?title=Bugfixing/en&oldid=911"