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

• Integration with Azure Boards
• Integration with Visual Studio 2022
• Automation using Pipelines and releases
• Real time dashboards
• Integration with code repositories

Incentivized

• It was difficult to create a branching strategy with GitHub. We had everything running from main, but in a true devops environment, we would like to incorporate a true branching strategy.
• I would like to share build projects with each AWS account we utilize versus creating a build project in each account. It will allow us consistent deployments across the board.
• The error logs are natively in AWS, but when developers do not have access, there is no way for them to view error logs for maintenance other than an admin who has access to share the error logs.

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

It is a highly usable, well integrated CI/CD service, patricularly for AWS-centric organizations. It is a strong balance between simplicity and flexibility. Security was integrated with AWS Secrets Manager allowing secrets to be retrieved dynamically - a huge usability win for us. I did not enjoy the manual build for each environment

Incentivized

I've used GitHub Actions compared to AWS CodeBuild - I enjoyed the integration with AWS from a codebuild perspective, but GitHub Actions and Workflows allowed us to create a reusable pipeline which is more in line with our devops structure. I enjoy AWS CodeBuild, but from a true continuous deployment, GitHub Actions was more fit.

Incentivized

Test rail feels quite dated compared to Azure Test plans and Devops as a whole. Functionality and ease of use is actually night and day.

The ability to create structured test plans with ease that can be traced and attached to Epics and stories with relevant tasks allows the system to feel superior in everyway compared to Test rail which had a slow web interface

Incentivized

• AWS CodeBuild was introduces as a core enabler for automating database deployments and enforcing a standardization across six environments. The standardization and quality control was well received.
• Security was baked in reducing audit findings.
• Deployments took minutes to update all environments compared to hours. It helped us a lot to reduce drift and deploy consistently.

Incentivized

• Typically the sprints themselves and managing the tasks have essentially eliminated our need for reporting.
• The most valuable features of Microsoft Azure DevOps are high-level protection. Protection is very important to the customers to prevent eavesdropping.

Incentivized