The earlier you find out about problems in your code, the less impact they have and the less it costs to remediate them. Therefore, it's helpful to move testing activities earlier in the software development lifecycle—shifting it left in the process timeline. This article explores the shift-left methodology and how you can approach shifting left in your organization.
Suppose we’re looking at a system rewrite where the stakeholders have none of the original engineering documentation. (This isn't surprising; documentation becomes obsolete—or even misleading—as the system changes, and corresponding docs don't get updated.) What can we do? Here are some tactics to use—and risks to anticipate—when testing a system rewrite.
There is a lot of talk in the testing world about shifting left. Basically, “shift left” refers to moving the test process to an earlier point in the development process, independent of the development approach. This article explores a case in which shift-left has been applied, and the lesson is that shifting left cannot be achieved by testers alone—it must result from a team effort.
Standard web-monitoring tools can ping webpages and verify that they’re responding, but they don’t alert you to an issue. But you can use the technology in load testing to monitor your sites by running an interactive script that can detect issues and generate emails as needed. It runs constantly like a silent sentry, never sleeping or taking a vacation, improving your sites' reliability.
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.
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.
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.
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.
In this interview, Alon Eizenman, the CTO and cofounder at SeaLights Technologies, discusses his many experiences with startup companies, how software teams are adapting to the current demand for speed, and why you need data before you take testing actions.
In this interview, LogiGear's Hans Buwalda explains how better test design can lead to improved test automation and can make the difference between automation success and failure. He details why successful automated testing is a test design challenge, not a technical challenge.
In this interview from STAREAST 2015, TapQA's Mike Faulise goes into detail on continuous integration and continuous delivery, the required technical skills needed to implement these methods, and how automation is embedded today.
Companies like Apple, Tesla, Google, Amazon, and Facebook have been investing in AI to solve different technological problems in the areas of health care, autonomous cars, search engines, predictive modeling, and much more. Applying AI is real, it’s coming fast, and it’s going to affect every business, no matter how big or small. How are testers going to adapt to this change and embrace AI? Join Raj Subramanian to discover how AI is going to influence the way we do test design and automation. He'll cover the basics of AI, the key ways software testing can benefit from AI, and the challenges involved in implementing AI solutions. This session will help anyone get started with AI-based testing.
Does it feel like you spend half of every sprint fixing failing automated functional tests? Are programmers unwilling to work with automation code? Is test automation a maintenance nightmare? There is a better way. The Page Object Model (POM) is a powerful design pattern for building test...