Difference between revisions of "Bugfixing/en"
Jump to navigation
Jump to search
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{languages|Bugfixing}} | {{languages|Bugfixing}} | ||
| − | '''Bugfixing is | + | '''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=== | ===Configure the bug finding and fixing environment=== | ||
| Line 15: | Line 21: | ||
::what data input? | ::what data input? | ||
| − | :2. Make the bug | + | :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. | The bug is considered "found" in all its extent if all platforms all situations, all etc. are tested or logically excluded. | ||
===Fix the bug=== | ===Fix the bug=== | ||
| − | + | *...or make a workaround | |
| − | Document the bug and its fix | + | *Document the bug and its fix |
| − | ===Have fix the | + | |
| + | ===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=== | ===Stage the fix to acceptance and production=== | ||
| + | Have the bug fix approved. | ||
==amenability== | ==amenability== | ||
| Line 30: | Line 39: | ||
==What actions cost time & expertise?!== | ==What actions cost time & expertise?!== | ||
| − | :1) Understand the whole application or module in depth before starting the | + | 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 | :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. | |
| − | 3) Create | + | :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. | |
| − | 4) Perform repeated tests with different test environment. | + | :6) Evaluate test data pattern to analyse the current set of tests. Reproduce all bug-patterns. |
| − | |||
| − | 5) Try to find out the result pattern and then compare your results with those patterns. | ||
| − | |||
| − | 6) | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
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...
Contents
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.
