The Task of Fixing Bugs: [Essay Example], 539 words GradesFixer
exit-popup-close

Haven't found the right essay?

Get an expert to write your essay!

exit-popup-print

Professional writers and researchers

exit-popup-quotes

Sources and citation are provided

exit-popup-clock

3 hour delivery

exit-popup-persone
exit-popup-close

Haven't found the right essay?

Get an expert to write your essay!

close
This essay has been submitted by a student. This is not an example of the work written by professional essay writers.

The Task of Fixing Bugs

Print Download now

Pssst… we can write an original essay just for you.

Any subject. Any type of essay.

We’ll even meet a 3-hour deadline.

Get your price

121 writers online

blank-ico
Download PDF

What do we usually do when we are given the task of fixing a bug. We start with root cause analysis, this is the general instinct that kicks in, when facing a bug. Not when you are doing TDD, not on the watch of XTreme Programming. XTreme programming advocates that developers should do things in a certain way, to be able to function smoothly and eventually have a shorter time to market. It is opinionated and strict about developer practices.

One of those practices is doing Test Driven Development. In this era of software development, there is enough recognition and accolades given to TDD, and yet there are people who believe its a waste of time.Assuming you have a fully functional team following XTreme Programming guidelines and doing TDD on a day to day basis, How would you fix a bug using TDD? These are the set of steps that you may follow to fix a bug using TDD :Reproduce the bug by introducing a failing End to End Test (Could be an integration test or an acceptance test, which not only limits to a single component).

Try reproducing the bug at unit level, by writing a failing unit test or multiple failing tests asserting that it is indeed an intra component failure.If you could come up with a test, that fails at unit level to reproduce the bug, then fix the bug at unit level, see if there are more tests(safety-nets) that you could introduce to cover boundary conditions.

See if your fix that passes the previously failing unit test, also passes the end-to-end test you wrote in step 1. (If not there is probably other problems, like configuration or maybe some other sub component which can also accommodate a failing unit test). If it passes then remove the end to end test, as the fix has nothing to do with integration – or keep it if it had. If you cannot find a way to introduce a failing unit level test in any component to reproduce the behaviour (un desired behaviour) then the problem probably lies in the configuration of your integration. If even your configuration is correct, then it is probably a false positive, or a contract broken by a third party, in which case you could still write a contract test, and a health check to avoid this in future, and have a clear indicator of what exactly failed. This is the broad overview of how you should try to fix the bug using TDD.

Then again there are exceptions like – If test is already there, but is not probably covering the behaviour thats failing, or some failure in infrastructure, but more or less this method will live up to XP’s philosophy(never repeat your mistakes, test everything) of fixing the bug in a way that ensures, that this will never happen again (Protection by test you just added).

Let’s end this article here, with a quote from Kent Beck.“However, most defects end up costing more than it would have cost to prevent them. Defects are expensive when they occur, both the direct costs of fixing the defects and the indirect costs because of damaged relationships, lost business, and lost development time.” – Kent Beck, Extreme Programming Explained: Embrace Change

Remember: This is just a sample from a fellow student.

Your time is important. Let us write you an essay from scratch

100% plagiarism free

Sources and citations are provided

Cite this Essay

To export a reference to this article please select a referencing style below:

GradesFixer. (2019, January, 28) The Task of Fixing Bugs. Retrived May 29, 2020, from https://gradesfixer.com/free-essay-examples/the-task-of-fixing-bugs/
"The Task of Fixing Bugs." GradesFixer, 28 Jan. 2019, https://gradesfixer.com/free-essay-examples/the-task-of-fixing-bugs/. Accessed 29 May 2020.
GradesFixer. 2019. The Task of Fixing Bugs., viewed 29 May 2020, <https://gradesfixer.com/free-essay-examples/the-task-of-fixing-bugs/>
GradesFixer. The Task of Fixing Bugs. [Internet]. January 2019. [Accessed May 29, 2020]. Available from: https://gradesfixer.com/free-essay-examples/the-task-of-fixing-bugs/
close

Sorry, copying is not allowed on our website. If you’d like this or any other sample, we’ll happily email it to you.

By clicking “Send”, you agree to our Terms of service and Privacy statement. We will occasionally send you account related emails.

close

Attention! this essay is not unique. You can get 100% plagiarism FREE essay in 30sec

Recieve 100% plagiarism-Free paper just for 4.99$ on email
get unique paper
*Public papers are open and may contain not unique content
download public sample
close

Sorry, we cannot unicalize this essay. You can order Unique paper and our professionals Rewrite it for you

close

Thanks!

Your essay sample has been sent.

Want us to write one just for you? We can custom edit this essay into an original, 100% plagiarism free essay.

thanks-icon Order now
boy

Hi there!

Are you interested in getting a customized paper?

Check it out!
Having trouble finding the perfect essay? We’ve got you covered. Hire a writer

GradesFixer.com uses cookies. By continuing we’ll assume you board with our cookie policy.