|
Making Visual Testing Visually Perfect: An Interview with Gil Sever Gil Sever, CEO at Applitools, discusses his journey in visual testing to making your product “visually perfect.” He talks about how companies are getting started in using automation, as well as how to get involved in leveraging and implementing AI in visual testing.
|
|
|
Moving to Progressive Web Development: An Interview with Eran Kinsbruner Eran Kinsbruner, mobile evangelist at Perfecto, discusses his new book and how to be successful in continuous and web testing. He talks about the importance of moving from responsive to progressive web development and taking it to the next level. Eran also shares his insights on AI and machine learning and the element of trust involved with each.
|
|
|
Why You Shouldn't Use Cucumber for API Testing Many people misunderstand the purpose of Cucumber. Because it seems to yield clearer, plain-language test scripts, testers want to use Cucumber as a general-purpose testing tool, including for API tests. But its true purpose is as a BDD framework. You may be thinking, what’s the harm? Here’s why it makes a difference—and why you should choose another tool for API testing.
|
|
|
Nontraditional Automation Using Fuzzy Browser Testing: An Interview with Paul Grizzaffi Paul Grizzaffi, Principal Automation Architect at Magenic, discusses nontraditional automation using fuzzy browser testing and the importance of the value stream analysis from idea to implementation. He also shares his insight on the most critical skills needed in automation.
|
|
|
How to execute the Test methods in different chrome instance using maven I have 5 testNg methods. It will take around 2 to 3 hours to complete the 5 test methods. So I want to execute each test methods in different chrome instance so that time will be reduced. Am executing the test methods using java main class by passing the series file which contains the class name.
|
|
|
The Simple Rules of Software Testing Simple rules are great for guiding us through an overwhelming workload. Sometimes complicated solutions are necessary, but simple rules often outperform complex algorithms, making them more efficient than sophisticated, difficult flows. They can also break down big goals into practical daily guidelines testers can follow to perform more effectively. Let’s see how simple rules can be applied in software testing.
|
|
|
Bringing AI into Testing: An Interview with Jeremias Rößler
Video
Jeremias Rößler, founder of ReTest, discusses his company’s open source re-check tool, how customer input was vital to the tool’s development, and shares insight on growing a start-up. Jeremias also provides resources for learning about AI that can guide you on how to apply AI into your testing strategy.
|
|
|
Test Everywhere: A Journey into DevOps and Continuous Testing A move to DevOps creates an opportunity to shift the testing process to the left. But what if you went further? DevOps supports continuous testing, so you can advocate for a constant focus on quality, with testing permeating the entire software development process. Here's how you can actually have a faster testing process when the software is tested throughout the lifecycle, by developers, testers, and automation alike.
|
|
|
Utilizing Containers to Improve Your Production Outcomes: An Interview with Melissa Benua
Video
Melissa Benua, engineering manager at mParticle, discusses the role that containers play in test environments. She answers questions like: Why do you need containers? How is your team going to benefit from containers? What is the first step in getting started with containers? Melissa provides resources for learning how to make a container and on how containers will aid you in maintaining control over data and code.
|
|
|
Dealing with a Test Automation Bottleneck The test team uses the test automation system to execute thousands of test cases because … why not? The tests are running automatically, for free, so there is no incentive to improve test efficiency. Just run them all! But eventually, as more and more tests are added, the system becomes overloaded. Test runs are delayed and you get a bottleneck. Don't throw more money—or new systems—at the problem; do this instead.
|
|