After the closure of the influential Epic v. Apple trial, a California judge has ordered Apple to immediately remove its anti-steering rules, which barred app developers from offering payment methods outside of Apple’s in-app purchasing system.

The three key positions in a software development team are developer, tester, and operations. Required tasks among these positions are continuously changing and evolving and are continuously changed and reinvented. To speed up the development process, development and operations were integrated, which is now referred to as DevOps. Unfortunately, a critical layer between Dev and Ops was overlooked: the fixed cycle of testing.

Picking the right performance testing tool can be a challenge. What should you look for and what is important? Performance testing is a phrase many developers have come across at some point, but what is it exactly? In simple terms, performance testing is a software testing practice used to determine stability, responsiveness, scalability, and most important, speed of the application under a given workload.

You can find a collection of k6 scripts and build specification for CodeBuild in this tutorial here.

Don’t worry. DevTestOps isn’t another new term to create turbulence in our IT and DevOps world. Similar to other topologies like DevSecOps, which emphasizes more on the “Sec,” or security matters, DevTestOps stresses the aspect of continuous testing and CI/CD in DevOps. At the same time, to uphold the culture of saying “no” to working in silos, the DevTest approach specifically aims to end the lasting bad blood between the development and testing teams.