Unit 4 - Test1

What is test coverage?

• Number of releases
• A measure of how much of the system is exercised by tests
• The number of team members
• Lines of code in repo
• Percentage of budget spent

Why have test data handling policies?

• To increase log verbosity
• To reduce RAM usage
• To speed up compilation
• To protect sensitive data used during testing
• To delete test cases

Which attachment documents known limitations?

• Team photos
• Invoice copies
• Contract templates
• Known issues or limitations log
• Marketing slogans

Which practice improves locating test items in large projects?

• Hiding items in folders
• Removing metadata
• Using random names
• Sharing passwords openly
• Maintainable naming and clear traceability

A good defect reporting policy should include:

• Steps to reproduce, observed and expected results
• Client testimonials
• Employee salary details
• Invoice numbers
• Release date only

Why include sample defect reports as attachments?

• To reduce test count
• To delete defects
• To encrypt logs
• To standardize reporting format
• To entertain readers

How should test items be uniquely identified?

• Using unique identifiers like IDs or tags
• Using same names for all
• Using random images
• Using calendar dates
• Using colors only

What is a primary objective of software testing?

• To increase development speed
• To replace documentation
• To encrypt data
• To detect defects
• To improve compiler behavior

What's a test strategy within the plan?

• Database schemas
• A list of coding conventions
• Vendor invoices
• User onboarding flow
• High-level approach to achieve testing objectives

Who are typical recipients of test reports?

• Project managers, developers, stakeholders and QA leads
• Random public
• Competitors only
• Children
• Catering staff only