PQ11

If you do a conscientious job developing software, your software should have no bugs when it is delivered.

False

You have to fix all the bugs in new, third-party software before you can continue with your development.

False

You will probably need to do spike testing on both third-party code and on code you developed yourself.

False

Which three of the following are presented by the textbook as the steps in spike testing?

Take a week to conduct your spike test. Pick a random sampling from the tests that are failing. At the end of the week, calculate your bug fix rate.

Pretty much all software has some bugs.

True

When making a bug fix estimate after a spike test, your team's gut feeling matters.

True

As you fix the relevant bugs in third-party code, every file you touch should come out of your cleanup with...

clear documentation

Functional code trumps beautiful code _____.

every single time

Real success is about delivering _____, period.

functionality

When trying to integrate third-party code that turns out to be buggy, the first step is to...

get it building

Whenever something changes during software development, talk it over with your team. If the impact is significant, in terms of functionality or schedule, then you've got to...

go back to the customer

If you got buggy third-party code, did a spike test, and determined an estimate to fix the bugs that you are reasonably confident in, what do you do next?

head back to the customer

"Naming a class with your company's name is a _____ idea..."

lousy

"Beautiful code is _____, but tested and readable code is delivered on time." Group of answer choices

nice

A spike test gives you ______ data upon which you can base your estimates.

quantitative

"When it comes to bug fixing, we ____ be sure."

really can't

Sometimes when integrating third-party code, there is lots of code that you don't directly use, and therefore don't test. Even if this untested code includes bugs, the textbook suggests that you focus on functionality and not obsess over testing this unused code. However, there is one exception to this rule. The exception is _____ issues.

security

By getting buggy third party software buildable and integrated into your development environment (including version control and testing harness), you have prevented all the problems the textbook describes from...

sneaking up on you and biting you

It's called _____ when you do one burst of testing activity to see what you get done in a specific time period, and using that to estimate how long it will take to do the entire testing and debugging of a piece of software.

spike testing

You know what code is broken because you have...

tests that fail

"If you'd be happy for someone else to read your code and rely on your software, then it's probably in good shape." The textbook calls this...

the pride test

According to the textbook, what is the relationship of a spike test and iteration length?

time for a spike test is not usually counted in an iteration

Get the code under source control and building successfully before you change anything... including fixing bugs.

true

Functionality is the focus. Only fix code to fix...

user stories