0% found this document useful (1 vote)
5K views

Continuous Deployment

Branch by Abstraction, Smoke Testing, and Binaries are techniques for large scale changes, testing types, and collections of executable codes, respectively. Continuous deployment aims to make feedback loops as short as possible by following continuous integration and representing dependencies with directed acyclic graphs. Acceptance testing is done in the Acceptance Stage to ensure the system works at a technical level before deployment.

Uploaded by

Venkat Reddy
Copyright
© © All Rights Reserved
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
0% found this document useful (1 vote)
5K views

Continuous Deployment

Branch by Abstraction, Smoke Testing, and Binaries are techniques for large scale changes, testing types, and collections of executable codes, respectively. Continuous deployment aims to make feedback loops as short as possible by following continuous integration and representing dependencies with directed acyclic graphs. Acceptance testing is done in the Acceptance Stage to ensure the system works at a technical level before deployment.

Uploaded by

Venkat Reddy
Copyright
© © All Rights Reserved
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 2

QUESTIONS

Large scale changes to an application can be achieved using _____ Branch by Abstraction
Capacity testing _______________. technical aspects
____________ testing was derived from hardware testing. Smoke
Collection of executable codes is known as ____________. Binaries
The continuous deployment must be followed to practice continuous 1
A build that fails __________ stage will not be deployable. Acceptance
Accurev is a _____________________________ system. Stream Based Version Control
A build can be triggered by a version control tool. 1
Build-time dependency should be present when an application is ru 0
People who do the deployment should be part of creating the depl 1
Build tools can be categorised as __________________. Both
Release candidate is created after the change passes through the Commit Stage
Continuous deployment aims at making feedback loops as short as 1
Dependencies between components must be represented using __ Directed acyclic graph
Time taken to fix a broken build is measured using _____________ Build repair rate
New instance of ___________ is created upon every check-in. All
What are the principle(s) that are basic for an effective configuration management?
A build is triggered whenever there is a change in the _________.
Disciplined technique for restructuring a code without modifying its external behavior is _________
User acceptance testing is done in the ______ stage. Manual Stage
Deployment pipeline is an extension of ______________. Continuous Integration
Component is separated from codebase when ______________.
Number of transactions a system can process in a given timespan, is measured using _____________
______________ is a non-functional test.
In branch by abstraction model, features are developed in _________.
___________ stage asserts that the system works at the technical level.
Response time of the requests are verified using __________________.
Feature toggles is possible in version control systems.
An environment that is in a properly deployed state is known as ____________.
Environment constitutes _________________________. All
Static code analysis is performed in the _____________.
Functional testing is a verification activity. 1
Automated implementation of an application's build, test, and deployment process is called as __
User acceptance testing is a verification activity. 0
Value delivered by an application is validated through __________ All
Testing done in a customer's environment is know as ____________ Beta
MTTR is
_____________________ is a paradigm to move code from check-in t Deployment Pipeline
Steps to be followed to release the application first time is part of Release Plan
__________________ stage takes the delivery team beyond continu Acceptance
Configuration information can be supplied using All
Only positive scenarios are validated in ___________ testing.
Trunk Based development

Both the options

TRUE
0
Task-Oriented
Acceptance Stage

Cyclometric dependency

Deployment Pipeline
Both
Both
Refactoring
Acceptance

All
Scalability
Performance
Feature Branch
Manual Test
Longevity Testing
1
Baseline

Unit Test

Continuous Integration

Mean Time to Repair

Hardware

You might also like