Reasons to Consider Software Tests as Products

4c3fcd213a759803b5a3adf18b9e7992a8fbb3b5e1bc9588b2pimgpsh_fullsize_distr

With DevOps, automated tests have become a crucial necessity. Tests need to be thorough, and their automation should be stable. In fact, tests have to meet quality and robustness criteria that are similar to the application under test, but tests seldom get the attention and investments that the applications get. Where sources and components of applications are considered products that are designed and developed, tests play a mere supporting role. In Scrum projects you will not see tests specified in the backlog. Rather, they are seen as a part of the production for the user stories.

Continue reading “Reasons to Consider Software Tests as Products”

Facebooktwittergoogle_pluspinterestlinkedinmail

Virtualization—A Tester’s Dream?

f0f8ffa8c3ccf2767cc02b53f88bbfbb5dcdf9848d21047c4bpimgpsh_fullsize_distr

Virtualization has been around for a long time. As early as the 1960s, IBM was supporting virtualization on mainframes to ease the cost of migration among multiple generations of their systems. Languages like Pascal, Java, and C# translate into virtual machine languages that are then either interpreted or further compiled (“just in time compilation”) into actual machine code.

Continue reading “Virtualization—A Tester’s Dream?”

Facebooktwittergoogle_pluspinterestlinkedinmail

DEVOPS IS COMING, ARE YOU READY?

devops-is-coming-are-you-ready

Just when you thought you were safe from more process improvement for a while—not so fast. There’s DevOps, Continuous Testing, Continuous Delivery and Continuous Deployment. In this issue, we are focusing on Continuous Testing, the part most concerning Test teams.

Continue reading “DEVOPS IS COMING, ARE YOU READY?”

Facebooktwittergoogle_pluspinterestlinkedinmail

What is CT and How Do Traditional Test Teams Fit In?

This article was originally published on DevOps.com

devops-for-test-teams

It wasn’t long ago that the Dev and test teams would work late hours, focused and rushed to meet a deadline: rapid fixing, reprioritizing and deferring bugs to close out the bug list, move everything to the staging server, do one last run of the regression and pass it over to Ops/IT to move to production. What happened after? No one knew. For most Dev and test team members, Ops is a black box. More often than not, they are oblivious to what happens at Ops, the roles, responsibilities and timelines. One day—long after the drop-dead deadline for Dev and test teams—after delays, questions and changes, the product went live. Continue reading “What is CT and How Do Traditional Test Teams Fit In?”

Facebooktwittergoogle_pluspinterestlinkedinmail