This is the set of 40 questions on Continuous Integration. What is Continuous Integration? here we go
Continuous Integration refers to the build and unit testing stages of the software release process. Every revision that is committed triggers an automated build and test. With continuous delivery, code changes are automatically built, tested, and prepared for a release to production.
source: AWS.
Please Note, the content that we are providing is based on our knowledge and personal study.
1. The time taken to fix a broken build is measured using_____________.
Ans: Build repair rate
2. _____________is a .Net build tool.
Ans: NAnt
3. Pipeline break and build break are one and the same.
Ans: False
4. The capability of your build system to handle an increase in the amount of code that it integrates and analyzes is known as_____________.
Ans: Build scalability
5. The complexity of a code is determined based on_____________.
Ans: Cyclomatic Complexity Number
6. _____________is a measure of incoming dependencies.
Ans: Apparent Coupling
7. Private builds are executed after moving the changes to version control.
Ans: False
8. Build can be triggered by a version control tool.
Ans: True
9. Release builds can be triggered _____________.
Ans: On-demand
10. is a continuous integration server.
Ans: Maven
11. Jabber is a :
Ans: Messaging plugin
12. Staged builds include _____________.
Ans: Secondary builds
13. The trunk is also known as_____________.
Ans: Mainline
14. The practice of developers integrating changes directly in the feature or work branches and committing the changes at the end to the mainline is known as _____________.
Ans: Continuous Integration
15. Faster feedback can be received by_____________.
Ans: Staging builds
16. Committing a code change, when the inspection fails, is perfectly fine as the code logic is working fine anyway.
Ans: False
17. Build can be triggered by a version control tool.
Ans: True
18. A control flow graph is used to calculate _.
Ans: Cyclomatic Complexity
19. CI pipeline consists of_____________.
Ans: Artifacts
20. Which of the tools is not used for establishing a pipeline workflow?
Ans: TeamCity
21. Arrange in order-
Ans: A. Running Unit Test B.Running Static Code Check C.Check for Code Coverage D. Build Package
22. Git, Mercurial, and Subversion are centralized version control tools.
Ans: False
23. How are component dependencies injected into a workflow?
Ans: Build the package first and then perform the remaining tasks
24. Staged builds include _____________
Ans: Commit builds
25. CI servers use the _ expression to poll for changes.
Ans: CRON
26. Efferent Coupling is a measure of.
Ans: Outgoing dependencies
27. TeamCity is a_____________
Ans: Build Tool
28. A component test is executed as part of _____________
Ans: Integration Build
29. CCMetrics is used to identify _____________
Ans: Code Complexity
30. Code changes can be hidden, enabled, or disabled using _.
Ans: Feature Toggles
31. Feature branching is used to____.
Ans:Work on user stories
32. Release branches are created for resolving merge conflicts.
Ans: False
33. Which is NOT a benefit of CI ?
Ans:Bugs and defects no longer occur
34. Activities that are part of continuous integration.
Ans: All of the Options
35. Which is not a CI practice ?
Ans: Deploy to production
36. Which is NOT true about continuous integration ?
Ans: Involves moving code in large amounts
37. Work Branch is also known as_.
Ans: Codeline
38. Git is a _ version control system.
Ans: Distributed
39. Does CI pipeline need to have all the software development functionalities integrated in place ?
Ans: False
40. Capablility of your build system to handle an increase in the amount of code that it integrates and analyzes is known as .
Ans: Build scalability