If you want to trigger long-running, end-to-end automated tests, you must integrate the test execution system with the continuous integration system. But this job falls in a fuzzy area that meets at the nexus of feature development, test automation development, quality assurance, and build and release engineering. Here's how to decide who should be responsible for the setup.
It’s usually easy and inexpensive to set up a continuous integration environment for either an agile or a waterfall project. Perhaps the most obvious benefit of CI is the elimination of the integration phase that existed in traditional waterfall projects, where we typically slip the worst on deadlines. But there are many other benefits to continuous integration that you may not have considered.
Bernie Zelitch writes that his company’s build system scales well because early on, they scrutinized their build naming convention, saw its implications to the build ecosystem, and made radical changes. Their new naming convention takes some getting used to, but once it was fully adopted, it improved economy, flexibility, and functionality.
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.
Never afraid to voice his opinion, Paul Gerrard suggests that in digital transformation projects, test automation may be the biggest challenge to success. He argues we have to get automation right this time and to do this, a new way of thinking about testing may be required.
There is no magic bullet to create an effective test automation environment. But Steve Gibson believes that creating a test automation vision, adopting metrics, and delivering value throughout a project lifecycle puts an organization on the right path.
Ryan Kenney, senior consultant at Coveros, chats with TechWell community manager Owen Gotimer about the difference between containers, container engines, and container orchestration; using containers in your CI/CD pipelines; and the cost of security.
Chris Loder, automation architect at InGenius, talks about being a self-taught automation developer, why learning new skills is so important, and the synergy between manual testers, automation testers, and developers.
Hans Buwalda's experience covers being a developer, manager, and principal consultant for companies and organizations worldwide. In this interview, Hans talks about using keywords effectively, tests that have too many details, and the changing testing industry.
One of the lines in the Agile Manifesto is "Working software over comprehensive documentation." This doesn't mean that no documentation is produced, but instead that only documentation that brings value to the team and the customer should be created.
Do you find yourself with limited influence over what gets shipped on products you test? Is your report card on product quality often ignored? Do you think you can contribute more? Join Gerard Meszaros as he describes ways to transition from approaching quality with brute force testing to...