Testing Flashcards
Examples of refactoring sections of code
1) Improving names of variables and functions
2) Placing sections of code where it is easier to read
3) Breaking large sections of code into smaller pieces with a logical flow
Test Plans
Should be created before development to include criteria to check by and test data to use
Black Box Testing
Checks whether an input produces the expected output - testers unaware of the internal structure of the code - carried out within the company and by end users
White Box Testing
Tests the internal structure of the code functions as intended - carried out by software development teams
Alpha Testing
Carried out in house by software development teams within the company where bugs are pinpointed and fixed
Beta Testing
Carried out by end users and feedback from users is used to inform the next stage of development
No data
No data is entered
Erroneous data
Data that is obviously wrong and should definitely fail / is the wrong data type
Invalid data
Data that looks like it should be fine but should be rejected by the system e.g. out of range
Boundary / extreme data
Data at either end of a range e.g. highest and lowest
Valid data
Data is not obvious but should still work
Normal data
Most obvious or common data that should work
When should a new row be added in a trace table?
If the state of a variable changes
