As the Agile environment has efficient principles that allow quick responses to changes and the ability to deal with uncertainty, exploratory testing may seem like a perfect match for such projects. However, this is only partially true. In reality, diverse reasons impede its usage in Agile projects, and companies should take them into account before designing QA strategies.
TDD is a software development approach in which a test is written before writing the code. When TDD is properly set up, it can bring numerous advantages and become a cost-saver, providing true value to the business. When TDD is not properly set up or without understanding how it should be used, it can be a waste of time and money. Quality comes not from inspection but from the improvement of the production process
Companies that want to reduce testing costs usually try working with fewer people, or even cutting back on the amount of testing done. But with those approaches, quality usually suffers. Releasing a critical bug and suffering the subsequent pain usually costs multiple times what testing would. There are better ways to save money, and it can be done just by being smarter about our test cases and their structure.
In the era of agile and DevOps, release decisions need to be made rapidly—preferably, even automatically and instantaneously. Test results that focus solely on the number of test cases leave you with a huge blind spot. If you want fast, accurate assessments of the risks associated with promoting the latest release candidate to production, you need a new currency in testing: Risk coverage needs to replace test coverage.
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.
Greg Paskal, evangelist in testing sciences and lead author for RealWorldTestAutomation.com, chats with TechWell community manager Owen Gotimer about testing as a craft, choosing the right test automation tools, and current testing trends around the world.
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.
Michael Bolton, principal at DevelopSense, explains why there should not be the perceived division between manual and automated testing. He says they are both just tools in a tester's toolkit, and we should use the tools appropriate to the job at hand.
Jeff Payne, CEO and founder of Coveros Inc., discusses the need for testers to incorporate security testing into development from the beginning. He also details some of the open source and commercial tools available for finding and resolving security problems.
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...