Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The best argument I've seen used is <strong><em>it is cheaper to fix bugs early</em></strong>.</p> <p>In particular, as you say, with short iterations untested code will almost certainly fail when deployed. Having the team stop to perform manual testing, then fixes, <strong><em>introduces uncertainty into the schedule</em></strong> when ideally the best practice of Scrum is that a well-defined rhythm of frequent high quality releases is what's needed.</p> <p>It can also be difficult to integrate untested code across a larger team: even the best written specifications can be ambiguous, and are frequently worse. Having a good robust test suite <strong><em>is a great specification for what the code actually does</em></strong>.</p> <p>Once the code has been written, decent test coverage lets you take code and <strong><em>change it knowing that it still works as defined</em></strong>. In particular the effort associated with regression testing is greatly reduced. </p> <p>I've seen management try to "cut corners" in this way by suggesting that testing is done outside of the core development function and away from the sprint cycle. In my experience that ends in tears, with the software delivered later than if proper effort was made to find and fix the bugs early.</p> <p>Perhaps it's a cultural issue, but in the UK the best practice I've seen for Scrum etc. is to not get too concerned with whether a particular part of the process is XP, Agile, Scrum or what-have-you. Rather, a policy of <em>inspect and adapt</em> suggests that a team can themselves decide to improve their code through adopting a particular policy; then, if after a spike it appears to work, the policy is adopted more widely. Or not. </p> <p>So, you may find it best to bide your time, then suggest improving test coverage at your next retrospective. Or, perhaps just implement them yourself... and watch your velocity improve!</p>
    singulars
    1. This table or related slice is empty.
    1. POWill a development process that doesn't emphasize automated unit tests get worse with Scrum?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJeremy McGee
    1. USJeremy McGee
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWill a development process that doesn't emphasize automated unit tests get worse with Scrum?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThis is a great answer. I'd only add that unit tests give you confidence to change code, which is a huge plus. It will be hard regardless of methodology if you don't have unit tests that prove code works as intended. Tests are an upfront investment that pay off later. The time that it takes to write the code is insignificant compared to the length of time you'll be maintaining that code.
      singulars
      1. PO
      1. USAndy
    2. COAll good points. I laugh at your mention of "improving test coverage". Code coverage is one of those "if I should live so long" topics here. Concerning the idea of just "do it myself", I believe it's the case that when developers "do it on their own", they appear to take longer to get things done, compared to the developers who just get it basically working, without writing unit tests.
      singulars
      1. PO
      1. USDavid M. Karr
    3. CO@Andy - most beancounters _hate_ the idea that code can change! But yes, I'll update my answer.
      singulars
      1. PO
      1. USJeremy McGee
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload