Open Testing: Opening Tests like Opening Source
Testing is a vibrant discipline with well-established practices, but many times, nobody but the testers who write the tests ever see them. Tests could offer so much value if they were openly shared—with developers, product owners, and perhaps even end-users. So, why don’t we open our tests like we open our source? There are so many parallel benefits: helping others learn, helping teams develop higher-quality software, and helping users gain confidence in the products they use. Opening tests includes sharing the tools, frameworks, and even test cases themselves. With AI and ML technologies, we could even build a future where generic open tests for common behaviors could run on any kind of app. In this keynote, we will look at ways a team could be more open about testing. Not every team may be able to publicly publish their tests, but any team could still benefit from the openings that shift-left practices can bring. Open Testing could be revolutionary. Let’s make it a reality!
Session Information
Time: 12:45 - 1:45
Room: West Ballroom (2nd Floor)
Andrew Knight
Andrew Knight
Andrew Knight is the Automation Panda and a Developer Advocate at Applitools. He strives to help others in solving problems in software development, testing, and quality. Over the past decade, he has designed and built robust test automation projects from the ground up that can run thousands of tests continuously. He is the author of the upcoming book "The Way To Test Software" from Manning Publications, and he is also the lead developer for Boa Constrictor, the .NET Screenplay Pattern. Read his tech blog at AutomationPanda.com, and follow him on Twitter at @AutomationPanda.