Site Search
Stretching your skills and preparing for organizational and work-related change is vital for any QA tester. Your best approach is to work on complementing your skills and competencies.
When software nears completion, it is the wrong time to focus on quality. Product delivery improves if you invest in a plan, validate in small increments, and focus on continuous testing.
QA testers often take on more of a role than just testing software code. When the team needs help, QA should lend a hand in assisting with business analysis, customer communication, user experience, and user advocacy.
Create tests that can be used in a continuous testing environment, build the right number of tests, and don’t fall victim to the mistaken belief that everything can be automated.
The internet of things (IoT) continues to proliferate as connected smart devices become critical for individuals and businesses. Even with test automation, performing comprehensive testing can be quite a challenge.
QA departments always feel the pressure to start testing quickly, even if the ever-changing software being tested isn’t ready. A bought-in test automation strategy can keep a project on track.
Because enterprise applications are highly interconnected, development in stages puts a strain on the implementation and execution of automated testing. Service virtualization can be introduced to validate work in progress while reducing the dependencies on components and third-party technologies still under development.
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.
How much testing is really enough? Given resources, budget, and time, the goal of comprehensive testing seems impossible to achieve. It’s time to rethink your test strategy and start innovating.
Some agile practices stress the importance of pairing team members together to achieve better team performance. Try these five suggestions for pairing key resources.
After setting up a DevOps team and adopting continuous delivery practices, product releases may not be as smooth as they could be. The missing ingredient requires empowerment and autonomy.
Has the rise in test automation resulted in product releases of lesser quality? Besides adopting more comprehensive automated scripting, there are process and organizational dynamics to consider.
Thanks to the trend toward DevOps and continuous delivery, traditional testing isn’t enough. Including test automation in your strategy is a good start, but your testing approach needs to change.
Agile teams enjoy focusing their time on product features while keeping documentation to a minimum. But every team needs to consider what documentation is really needed. How much is enough?
Customers expect fast-paced, quality product releases. To meet these demands, you must consider test automation, testing in production, and the extensive use of data and analytics.