Test Engineering culture emphasises on quality ownership by all involved in a project and redefines the role of testers as engineers as quality enablers instead of gate keepers. This talk shares the experience to build a test engineering culture across the organization, how does it vary with the size of the team and the company and the role of software testersin building this culture by enabling others with tools and processes for quality improvements.
People are the most important success (or failure) factor in software development projects. This is also true in the software testing field. In his article “Testing Your Emotions”, Stephen Janaway explains why it is very important that software testers understand their emotions as they can be a great heuristic to guide testing.
Most of us have had to deal with red builds blocking our testing or have been told to test on flaky environments where half the issues you find would ‘never happen in production’. As a tester, I used to think this wasn’t my problem. What happens though when a thinking tester decides this is her problem and wants to be part of the solution?
The software industry is changing fast. Many of the companies software testers work for have to re-adjust their working patterns, release cycles and project approaches in response to this change. It’s never been more important to remain relevant to the company you work for. Yet a surprising number of people are ignoring the needs of the business they work for, clinging to outdated approaches to work and running away from change.
Software testing is an activity that has often been placed at the end of the software development life cycle, something that you did if there were some time left before the project deadline. In his book ” Scrum Shortcuts without Cutting Corners”, Ilan Goldstein explains that the software testers should be active since the beginning of the project.
It is not always easy to have management responsibilities in software development and software testing when you come from a technical position. This is also true in software testing. In this article, Mark Garzone shares some tips on how to be a better software testing team lead or test manager.
Code coverage is a metric that gives the degree to which the source code of a program is tested by a particular test suite. This metric is provided by open source or commercial code coverage tools and displayed in quality dashboards like SonarQube. There are many discussions about the right level of code coverage. In his book Quality Code, Stephen Vance explains the limit of this metric.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates