NEW
Font size
WorksheetsModule 6: QA Best Practices for Code Assurance
Total questions: 25
Worksheet time: 8mins
What is the primary purpose of coding standards in a development team?
To restrict who can write code
To define deployment schedules
To provide shared rules for how code is written and structured
To replace automated testing tools
Which of the following is NOT a benefit of coding standards?
Improved readability and consistency
Easier onboarding of new contributors
Increased dependency on individual developers
Simplified long-term maintenance
Why do consistent coding standards reduce errors?
They eliminate the need for testing
They remove ambiguous or inconsistent patterns
They automatically fix bugs
They enforce faster deployments
What is the main goal of contribution guidelines?
To automate code reviews
To explain how to contribute to a repository clearly
To manage production releases
To monitor repository metrics
Which topic is typically covered in contribution guidelines?
Server infrastructure configuration
Branching strategy and pull request rules
Marketing documentation
End-user licensing terms
How do contribution guidelines improve code quality?
By enforcing deployment approvals
By reducing friction and setting clear expectations
By replacing branch protection rules
By preventing collaboration
What is the primary purpose of branch protection rules?
To speed up merging
To safeguard critical branches from unreviewed changes
To automate documentation updates
To allow direct commits to main
Why is branch protection important for QA?
It allows bypassing reviews
It enforces controlled review processes
It reduces the need for testing
It simplifies contributor permissions
What is a key function of required reviews?
Automatically merging pull requests
Ensuring peer examination before merge
Blocking automated testing
Reducing repository visibility
How do required reviews improve code quality?
By enforcing individual ownership
By catching logical or design issues early
By replacing linting tools
By increasing merge conflicts
What role do status checks play in pull requests?
They notify users of new branches
They act as quality gates before merging
They manage contributor access
They replace code reviews
Which is a key benefit of status checks?
Allowing merges even when tests fail
Blocking merges when automated checks fail
Reducing CI execution
Disabling linting tools
Why is automated testing critical in pull request workflows?
It replaces peer reviews
It validates changes before merging
It speeds up manual testing
It removes the need for QA processes
What is the main purpose of linting tools?
Detect runtime errors in production
Enforce style and formatting standards automatically
Deploy applications
Manage pull request approvals
How does linting improve pull request reviews?
By increasing review time
By reducing time spent on style issues
By replacing automated tests
By blocking all merges
What happens when automated tests and linting are configured as required checks?
They become optional
They act as mandatory quality gates
They run only after merging
They replace branch protection rules
Which practice is part of making automation a mandatory quality gate?
Ignoring failed checks
Blocking pull requests when automation fails
Allowing manual overrides without review
Running tests only on release branches
What does repository health indicate?
Hardware performance
Effectiveness of code quality and collaboration practices
Number of contributors
Programming language popularity
Which is a key repository health indicator?
Number of stars
Stability of protected branches over time
UI theme settings
Contributor geographic location
Why is monitoring team activity important?
To limit collaboration
To identify bottlenecks and improve workflows
To reduce transparency
To eliminate metrics tracking
Which metric is commonly used to evaluate QA effectiveness?
Commit message length
Pull request review and merge times
Number of emojis in comments
Repository size
Why are metrics only valuable when paired with action?
Metrics automatically fix issues
Insights must lead to workflow improvements
Metrics replace coding standards
Metrics remove the need for reviews
What is the purpose of a CONTRIBUTING.md file?
To document deployment secrets
To standardize contribution and quality expectations
To store test results
To configure CI pipelines
What does a green play icon in the GitHub branch protection UI indicate?
The branch is deleted
The ruleset is enforced
Reviews are optional
Automation is disabled
Why might a pull request be blocked even if all automated checks pass?
Missing documentation
Branch protection requires at least one approving review
Too many commits
Linting tools are disabled
