For most enterprise software development projects, software testing is not really fun. It is boring, cumbersome, and takes time and effort — especially for distributed applications or when changes in existing functionality forces test scenarios to adapt. Still, software tests are crucial; so, how can we tackle them in an effective and productive way?
Software Testing Videos and Tutorials: Load Testing, Unit Testing, Functional Testing
Botium is a quality assurance framework for testing and training conversational AI. This presentation covers the Selenium driver for Botium to automate E2E tests on Web UI and mobile along with testing strategy, testing NLP models and automating these tests to the CI/CD build pipelines with a DialogFlow based ‘Coffee-Shop bot’ as an example during the demo.
This presentation puts the role of the software tester under the microscope and discusses how software testers can learn from the research and work that criminal investigators do today, how to use hard facts, as well as hidden facts, to determine a trustworthy conclusion.
This video shares strategies for successful automation, the challenge of flaky tests, the perils of UI automation, and many other tips based on experience in test and test automation across dozens of high volume products. Whether you are deeply invested in test automation, or just getting started, learn practical tips you can apply to your own testing efforts immediately.
In the new world of pipeline based organizations, software developers, software QA, operations, security and others people involved in software development are required to take on new skills and develop new collaboration strategies in order to support automated delivery pipelines. This talk shares important insights to help guide software testers on that journey.
The bigger question for software development teams embarking on their test automation journey is “What to test?” My rule of thumb is “Start with the scariest code”. This presentation shares with you a framework for evaluating the ROI of writing a test for a feature and prioritizing what to test.
A couple of years ago, Endava realized that the difficulties in DevOps adoption are never the automation technology but rather the ways-of-working, which require a much more fundamental change in people’s behavior and culture.