A. The person who broke the build
B. The next person who needs the build to complete successfully
C. The tester responsible for validating builds
D. The person who is responsible for configuration management within the team
A. Includes exercising the persistence layer
B. Makes assertions about only one logical concept
C. Independent of others
D. Execution is fast
A. In production during peak hours
B. Just before deployment to production
C. Often during the development
D. In production
A. A test object that mimics the behavior of a dependency in the system under test
B. A mock is a way to initialize the database for testing
C. Mocks, stubs, dummies, fakes and shims are all the same
D. A mock helps you create a build script
A. The last moment a Developer is responsible for quality; after this, the Tester is responsible.
B. Making decisions as soon as possible to close feedback loops as soon as possible.
C. Discover decisions to be made as soon as possible but postpone making those decisions until the latest reasonable moment.
D. The last moment in a Sprint when code changes are allowed; after this, only stabilization work should be conducted.
A. Product owner
B. Scrum master
C. QA specialists
D. The tester
E. Developers
F. Most junior developer
A. Reduce effort and risk when integrating changes.
B. Know immediately how a change affected the product.
C. The feature-branch is generally kept in a buildable state.
D. Readability of code is improved.
A. Creating a plan for the entire project
B. Work together and self manage to create value
C. Create a potentially shippable functionality in the sprint
D. Design the full architecture before starting
A. It depends on the product owner
B. Every team uses its own. The differences are discussed in a hardening sprint.
C. All development teams must have a DoD that makes their combined work releasable.
D. Every team must make their own DoD, a meeting should be organised so that the differences are known.
A. From the beginning and throughout the sprints, but let's call them developers
B. After every sprint review
C. When the developers are done
D. When the product is complete
