Tip: Choose Save as PDF in the print dialog to download. Use A4 paper size.
Shade in the A or B circle for each question.
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 1black box test | ASource code and network diagrams are full knowledge, which belongs to white box testing. A black box tester starts with no inside information. | |
| 2white box test | BThe tester starts with no inside knowledge and attacks like an outsider, seeing only what the public can see. | |
| 3A grey box tester has partial knowledge, like a normal user or employee who has a login but not the source code. | Cknowledge = {'black': 'none', 'grey': 'some', 'white': 'all'} | |
| 4The three approaches differ in how much the tester knows about the target system beforehand. | DKnowing only a public address is outsider knowledge, which belongs to black box testing. A white box tester has full inside knowledge of the system. | |
| 5black box test: tester is given the source code and network diagrams | Etester_knowledge = 'partial: user login only' | |
| 6white box test: tester only knows the company's public website address | FThe tester is given full knowledge of the system, such as source code, network diagrams and configuration details. |
Complete each line of code by filling in the missing parts.
Shade in the letter of the line that contains an error.
Black, grey and white box testing — Test approaches defined by what the tester knows beforehand: black box knows nothing (outsider view), grey box knows some (insider view), white box knows everything (full knowledge).black box testing: tester knows nothinggrey box testing: tester knows some detailswhite box testing: tester has full knowledgeBlack box view: like an external attackerGrey box view: like an insider user