Development teams that shift testing left discover bugs earlier, enhance developer productivity, and increase release velocity by avoiding the long and costly delays that occur when bugs are discovered at the end of the development cycle. Shifting left creates faster feedback loops and allows for faster bug remediation.
Faster DevOps processes also create new challenges. It was difficult enough to add security into a traditional waterfall software development lifecycle with monthly or quarterly releases, but now software updates are released several times a day! What can developers do to build and maintain more secure applications? Here are some ways to encourage better security practices throughout the DevOps lifecycle.
Testers and developers often have a strained relationship. Each side has a certain level of expectations as to what the other side should know and do, while there is little understanding of the constraints, conditions, and requirements that the other team has to work within. But it does not have to be this way. A little effort in giving more specific and helpful feedback can go a long way toward improving attitudes.
Many organizations are looking to expand their automation abilities by designing and developing test automation frameworks. However, we often abandon good coding practices in favor of working as fast as possible. We need to treat this project like any other application development project. Here are three of the most important clean coding practices to keep in mind in order to make a scalable test automation framework.
Migrating an organization to continuous integration requires adoption new processes, tools, and automation. DevOps relies on dramatic culture change to encourage total transparency and collaboration among all project stakeholders.
Melissa Benua, director of engineering at mParticle, chats with TechWell community manager Owen Gotimer about the importance of whole team quality, how to get started using the test pyramid, and how developers can start writing testable code.
Aprajita Mathur, bioinformatics software test manager at Guardant Health, discusses how to develop yourself and why it's so important to take the time to do so. She explains that your personal life will always be more significant than any work you need to get done, and she gives strategies for how to talk with your manager as well as your team when you are feeling overworked and need a break. Aprajita believes if you are self-aware and have open communication, then having these conversations will be easier and you can focus on yourself.
In this interview, Michael Faulise, the founder and managing partner at tap|QA, explains how the move toward DevOps and away from release management is giving control back to developers, then details why major companies often need partners to leverage CI, CD, and other modern techniques.
In this interview, Hans Buwalda, the CTO at LogiGear, explains how software developers have the mindset of creation while software testers are more concerned with how things might be destroyed. He details why testers don’t always need to code and why UI and API automation matters.
State Farm adopted an innovative approach to a common problem many organizations face with agile transformation: How do you influence, nurture, and support a whole scale culture of agility? How do you move from doing agile to being agile?
Behavior-driven development has been a buzzworthy term in the testing and development community for several years. At first glance, the elements of BDD seem simple: testing scenarios, living documentation, automation, and reports.
y now you have probably heard that there should be a healthy tension between the product and engineering teams. The key word there is "healthy"—when this relationship is unhealthy, silos tend to form, ideas may be thrown over the wall, and a lack of ownership can develop.
Kubernetes is one of the fastest growing open source projects in history, and it's taking the DevOps world by storm. With so many resources being poured into this technology, it would be nice if there were some benefits for testing.