Difference between revisions of "Bugfixing/en"
(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...") |
|||
| Line 2: | Line 2: | ||
'''Bugfixing is letterlijk het oplossen van fouten. In praktijk betekent het echter veel meer...''' | '''Bugfixing is letterlijk het oplossen van fouten. In praktijk betekent het echter veel meer...''' | ||
| − | + | ==Bugfixing consists of== | |
| − | + | ===Configure the bug finding and fixing environment=== | |
| + | Precondition is you have your personal development environment in place. | ||
| − | 2) Prepare good test cases before start to | + | ===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 reproducable | ||
| + | |||
| + | 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 bugfix tested=== | ||
| + | |||
| + | ===Stage the fix to acceptance and production=== | ||
| + | |||
| + | ==amenability== | ||
| + | <small>From: http://www.softwaretestinghelp.com/how-to-find-a-bug-in-application-tips-and-tricks/</small> | ||
| + | |||
| + | ==What actions cost time & expertise?!== | ||
| + | :1) Understand the whole application or module in depth before starting the testing. | ||
| + | :2) Prepare good test cases before start to test | ||
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. | 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. | ||
Revision as of 10:31, 10 July 2012
| Language: | Nederlands • English |
|---|
Bugfixing is letterlijk het oplossen van fouten. In praktijk betekent het echter veel meer...
Contents
Bugfixing consists of
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 reproducable
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 bugfix tested
Stage the fix to acceptance and production
amenability
From: http://www.softwaretestinghelp.com/how-to-find-a-bug-in-application-tips-and-tricks/
What actions cost time & expertise?!
- 1) Understand the whole application or module in depth before starting the testing.
- 2) Prepare good test cases before start to test
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.
4) Perform repeated tests with different test environment.
5) Try to find out the result pattern and then compare your results with those patterns.
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.
7) Use your previous test data pattern to analyse the current set of tests.
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.
9) Last and the best trick is try very hard to find the bug ;-) As if you are testing only to break the application!
