Term
After a new feature is added ____ testing is often performed to verify no new bugs have been introduced in the existing features |
|
Definition
|
|
Term
To reveal any problems with the game’s user interface, ___ testing was done |
|
Definition
|
|
Term
To verify that all boundary conditions and code paths had been tested, the test engineering group did ___ testing, while analyzing hte source code |
|
Definition
|
|
Term
To verify that the flight software simulator could handle error conditions, special ___ testing was done |
|
Definition
|
|
Term
A careful programmer will perform ___ testing before checking their work or giving it to the QA group |
|
Definition
|
|
Term
Another name for ___ testing is function or data-driven testing |
|
Definition
|
|
Term
To verify that response time and throughput would meet the custom requirements for the graphics subsystem, ____ testing was run |
|
Definition
|
|
Term
to expose the holes that hackers might use to break into the online role playing server, _____ testing was done |
|
Definition
|
|
Term
to determine whether the massive multiplayer online games could support tens of thousands of concurrent users, the QA group performed ____ testing |
|
Definition
|
|
Term
Before the first person shooter could ship on the Xbox 360 it has to pass microsoft ___ test |
|
Definition
|
|
Term
|
Definition
uninitialized stack memory |
|
|
Term
|
Definition
freed heap memory (after HeapFree()) |
|
|
Term
|
Definition
uninitialized heap memory |
|
|
Term
|
Definition
memory beyond the bounds of allocated memory |
|
|
Term
|
Definition
|
|
Term
|
Definition
freed heap memory before HeapFree |
|
|
Term
Describe three strategies for tracking down the source of a bug |
|
Definition
Simplify the problem
perform a source code inspection
isolate the problem |
|
|
Term
Explain the reason behind the "Quit Thinking and Look" rule in David Agans' book |
|
Definition
Collect data before trying to fix the problem, don't just make guesses |
|
|
Term
Using hte waterfall mdoel, list the life cycle stages that a software product typically goes through |
|
Definition
Requirements->
Design->
Implementation->
Integration->
Testing ->
Release ->
Maintenance |
|
|
Term
|
Definition
storage location from which software packages may be retrieved and isntalled on a computer |
|
|
Term
|
Definition
|
|
Term
|
Definition
am application, operating system, computer, or appliance |
|
|
Term
|
Definition
software that accesses a remote service or another computer |
|
|
Term
|
Definition
point in a computer program where program-flow may change depending on a condition |
|
|
Term
|
Definition
synchronization mechanism enforcing limits |
|
|
Term
|
Definition
a list of changes made to a program |
|
|
Term
|
Definition
a local, version controlled copy of a repository's files and directories |
|
|
Term
|
Definition
upload files to a repository |
|
|
Term
List and briefly explain six types of common coding errors |
|
Definition
Memory leaks - not deleting memory
variable overflow - wraps around
null or invalid pointers - uninitialized pointers
uninitialized memory - no memory has been allocated
off by one loop - index is off by one, may cause an out of boudns error
unintended infinite loops - program is stuck in a loop forever where it is not supposed to be
Faulty math or logic - you did an algorithm incorrectly |
|
|
Term
describe at least five desirable software qualities |
|
Definition
Reliable(does not crash or behave erratically)
Efficient (responds quickly to the user)
Easy to Use (reading a manual is unnecessary)
Fun to Play! People can enjoy it
Portable (can be ported t multiple platforms)
|
|
|
Term
Descrive at least three reasons why a source control system is helpful |
|
Definition
different people can work on things at the same time
you can merge files quickly
revert back to an old version
everyone can work on the same solution
|
|
|
Term
Explain the difference between black box and white box testing |
|
Definition
white box uses code to test the program, black box does not |
|
|
Term
Describe the difference between positive test cases and negative test cases |
|
Definition
positive is testing with values it's supposed to get right
Negative values are used to purposely break
|
|
|