STARWEST 2018 - Developer

Testing and requirements are bound together: You use requirements to understand what to test and what your customer expects from the product under test. Requirements appear in many forms—verbal, diagrams, user stories, or formal specifications. But sometimes once we start testing, we find that requirements are missing, inadequate, wrong, or changing. This is normal, and as testers, part of our role is to help the team and the customer clarify what is required. (Sometimes we even build the requirements to clarify our tests!) Join Isabel Evans to understand how to identify, capture, review,...

Docker is one of the hottest technologies in our industry today. It lets you create and manage containers—like virtual machines but smaller and faster. They can provide on-demand, disposable test environments that start quickly, repeatably, locally or in the cloud. When you want, you can tear down the environment and recreate a pristine copy within seconds. And since the process is automated, anyone on the team can use the same commands to get their own test systems. Then, when you finish testing, those containers can be deployed directly into production. At each stage, the environments...

Software development is trending toward building systems using small, autonomous, independently deployable services called microservices. Leveraging microservices makes it easier to add and modify system behavior with minimal or no service interruption. Because they facilitate releasing software early, frequently, and continuously, microservices are especially popular in DevOps. But how do microservices affect software testing and testability? Are there new testing challenges that arise from this paradigm? Or are these simply old challenges disguised as new ones? Join Tariq King as he...

Imagine this … As soon as any developed functionality is submitted into the code repository, it is automatically subjected to the appropriate battery of tests and then released straight into production. Setting up the pipeline capable of doing just that is becoming more and more common and something you need to know about. But most organizations hit the same stumbling block—just what IS the appropriate battery of tests? Automated build architectures don't always lend themselves well to the traditional stages of testing. In this hands-on tutorial, Melissa Benua introduces you to key test...

Artificial Intelligence (AI) is making it possible for computers to diagnose some medical diseases more accurately than doctors. Such systems analyze millions of patient records, recognize underlying data patterns, and generalize them for diagnosing previously unseen patients. A key challenge is determining whether a patient's symptoms and history are attributed to a known disease or other factors. Software testers face a similar problem when triaging automation failures. They investigate questions like, Is the failure due to a defect, environmental issue, or nondeterministic test script?...

Sometimes we allow ourselves to drown in work… Mary Thorn hears it all the time: testers complaining at retrospectives to their teams that they do not have enough time to test everything. She often sees testers work overtime the last week of a sprint to ensure the definition of done is accomplished. Why do they do this? Why do we, as testers, enable the bad behaviors of “Scrummerfall” or a lack of whole-team ownership of quality? Mary aims to arm testers with techniques that allow them to test smarter, not harder, and enable the testers and the team to have better conversations that make...

Although processes and tools play an important role in software testing, the most important testing tool is the mind. Like scientists, testers search for new knowledge and share discoveries—hopefully for the betterment of people’s lives. More than sixty years ago, William I.B. Beveridge reframed discussion of scientific research in his classic book The Art of Scientific Investigation. Rather than add to the many texts on the scientific method, he focused on the mind of the scientist. Join Ben Simo as he applies Beveridge’s principles and techniques for scientific investigation to software...

When Isabel Evans learned to drive a car, she also learned how to check, clean, and change spark plugs, mend the fan belt with a stocking, and indicate speed and direction changes with arm and hand signals. Now, we don’t expect to have to do any of those things; we just drive the car. That’s how test tools and automation could be. Just drive and concentrate on the journey of delivering software continuously—concentrate on engineering the solutions, not on the automation. To be effective engineers, we need the support of a powerful toolset that we understand. Is that what we have? Or do we...

Testing is shifting left, moving closer to testing the code itself before the full product is ready for release. While the backend world already has established methodologies for testing, frontend developers and testers are still trying to figure out how to work together to effectively test the code. Gil Tayar suggests testers need to communicate with the frontend developers to understand the framework by which frontend code is tested, the various kinds of testing that can be performed on frontend code, and which tools can be used. During this session, Gil helps ease your fear of the...

The DevOps movement is front and center across enterprises. Companies with mature systems are breaking down siloed IT departments and federating them into product development teams and departments. Testing and its practices are at the heart of these changes. Traditionally, development organizations have been filled with mostly manual testers and a limited number of automation and performance engineers. Adam Auerbach says this has to change. To keep pace with development in the new “you build it, you own it” environment, testing teams and individuals must develop new technical skills and...

In a busy world, testing teams are asked to adopt new approaches to increase speed and flexibility of change. What methods and tools can help? Artem Golubev has seen many testing teams being told to use Docker. But for testers, this brings confusion. What it Docker and why is Docker useful to testers? How can Docker be used to increase confidence in our releases? To help you answer those questions, Artem shares his experience using this popular tool and approach. Starting with terminology Artem shares what is meant by Dockerfile, Docker Image, Docker Container, Compose, Kubernetes...

Everybody wants to have their projects tested so that they can deliver top-notch products to their clients. But with multiple projects all running in parallel, all with tight deadlines and all needing testing, simply allocating a tester on a project for some time isn’t going to give you quality. This, in turn, can sometimes make our stakeholders question the value of testing. Join Nimesh Patel as he shares his experience in building a test practice and team from the ground up into valued, credible members of a project, in a digital agency where the focus is often on delivering...

Performance issues substantially impact quality, cost, and customer confidence. Agile teams are challenged to build in performance processes throughout the lifecycle, but it is critical to incorporate performance into your CI/CD pipeline. Join Amit Patel as he shares his recent project experiences and the steps his team took to change processes, leverage different technologies, and align internal stakeholders. He explains how they use production-monitoring solutions to create a real-world production feedback loop in order to ensure they can analyze data and turn the information...

Articles on abc.net and elsewhere reported that Volvo has recently discovered a non-traditional requirement: Any self-driving vehicle approved for use outside Australian cities must recognize kangaroos on or near the roadway and take proper actions. The kangaroo’s bounce confused the large animal detector! In this session, industry expert David Gelperin shares a new perspective on the value of imprecise requirements and explores the nature of testing them. Excess precision may hamper the development of optimal solutions by excluding effective designs. Imprecise statements reduce the risk...

Does test automation need traditional test cases? Mehmet Duran says no. Using the open source tool TESTAR, he devised an innovative approach to automated testing. Join Mehmet as he shares the research he conducted to solve this challenge and how he confirmed his findings by comparing test approaches using a new framework with the quality attributes of learnability and usability. Mehmet will also describe he worked with Hatim Chahim of Prorail on a real-world railroad project to try out his theory. After applying the framework, results showed that within this setting, the test automation...

When the atmosphere is hostile to QA, and yet the demands on the QA Team are increasing, how do you transform a team where everything is tested and deployed manually, to an organization that delivers great software multiple times a day? Where do you start and how do you create the strategy for implementing Continuous Testing? Join David Lumpkin as he shares his company's journey to answer these questions and the team's evolution along the way. Over a three-year period, Craftsy went from an environment hostile towards QA, to one that embraces automation and exploratory testing,...

Risk-based testing is essential to focus our testing, but it is not always easy to apply to our projects. Risk management tends to focus more on project and process risks (i.e., Will we make the deadline? Do we follow our processes?) and less on the product risks that can act as a foundation for a risk-based approach to test. Including this aspect of risk in your test coverage will give you a solid foundation for defining a test strategy that implements and executes the right tests with the right intensity to mitigate the most critical product risks. In this presentation, Gitte...