 
 <prompt> text: ```As di number of possible tests for even simple software components dey practically infinite, all software testing dey use some strategy to select tests wey dey feasible for di available time and resources. As a result, software testing typically (but not exclusively) dey try to run program or application with di intention of finding software bugs (errors or other defects). Di work of testing na iterative process as when one bug dey fixed, e fit show other, deeper bugs, or fit even create new ones.

Although testing fit determine di correctness of software under di assumption of some specific hypotheses (see hierarchy of testing difficulty below), testing no fit identify all di defects within software. Instead, e dey provide criticism or comparison wey compare di state and behavior of di product against oracles—principles or mechanisms by which person fit recognize problem. These oracles fit include (but no dey limited to) specifications, contracts, comparable products, past versions of di same product, inferences about intended or expected purpose, user or customer expectations, relevant standards, applicable laws, or other criteria.

Based on di article and di following list of answers, write a list of questions.

1. possible tests
2. software bugs
3. no
4. e fit show or create new ones
5. no
6. e dey provide criticism
7. yes
8. more than eight
9. run program
10. iterative

Numbered questions:``` <response>: ```1. Wetin be infinite?
2. Wetin these tests dey find?
3. Once e don fix, everything dey okay?
4. Why e no dey okay?
5. Testing fit identify everything?
6. Wetin e do instead?
7. Contracts dey inside the oracles?
8. How many things be oracles?
9. Wetin software testing dey try do typically?
10. Wetin type of process be the job?``` 