Difference between revisions of "Bugfixing/en"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
{{languages|Bugfixing}} | {{languages|Bugfixing}} | ||
| − | '''Bugfixing is | + | '''Bugfixing is literally solving a problem. However bugfixing consists of a lot more...''' |
==Bugfixing consists of== | ==Bugfixing consists of== | ||
Revision as of 10:37, 10 July 2012
| Language: | Nederlands • English |
|---|
Bugfixing is literally solving a problem. However bugfixing consists of a lot more...
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 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.
- 7) Evaluate test data pattern to analyse the current set of tests. Reproduce all bug-patterns.
