AWS CodeBuild vs. Azure Test Plans

It is really good for building projects in the cloud. If you try to do build the project first locally and then push that stack to the cloud it could take a lot of time. In this way, it also consumes a lot of resources in the computer and in the network.

Incentivized

It works well for express test case implementation with a short duration. You can define the tests for two weeks and run the activities documenting the software errors and fixes to control the effectiveness of DevOps. The graphic reports give the idea of the backlog phases advances and errors detected. It needs improvement if you have a large test project and need to design financial budgets and control over costs of the test plan.

Incentivized

• Customization
• Do code builds within a schedule or when the source code changes
• Only pay for the build time used

Incentivized

• Multi test plan access
• Well structured and easy to use
• Integrates with other azure features to work seamlessly ,connecting the data flow

Incentivized

• Sometimes it runs an outage and developers don't know why. We have to contact DevOps most of the time.
• Sometimes it is slow

Incentivized

• Graphic definition of the the Work Break Down Structure
• Gantt Chart to check the activity dependance and flow of the process
• Basic cost module to design test budgets.

Incentivized

AWS CodeBuild provides the option to fully implement the build in the cloud without wasting your local resources (computer and network) providing independence to developers to invest those resources in other processes. It also provides a robust platform with a lot of customizations or just a script for each language.

Incentivized

We're doing a full continuous integration (CI), continuous delivery (CD), continuous testing (CT), security, delivery, and monitoring. They have been lately adding features to the services on a regular basis. Every two weeks, they add functionality to Azure DevOps Services to match it with what Azure DevOps Server or on-prem would offer. So, we continue to get more robust functionality. My favorite right now is that they are starting to open up the API availability within Azure DevOps Services.

Incentivized

• It has a positive ROI

Incentivized

• Pros: One stop solution for end to end traceability
• Pros: Exploratory testing used
• Pros: maximum coverage on multiple browsers, operating system combinations
• Cons: Integration with Non-Microsoft tools can be improved

Incentivized