The Latest
From Zero to AI Hero[presentation]
Slideshow
AI is here. Will it take over your job? Is it possible to make it beneficial, not detrimental to your career? Kevin Pyles and his team jumped right into the AI universe. Untrained and inexperienced, they realized immediately that they knew nothing. |
Kevin Pyles
|
|
Fuzz Testing for Fun and Profit[presentation]
Slideshow
A test is no better than the data that drives it. Fuzz testing is a great way to find buggy, exploitable, or otherwise bad code – and if you’re working with a native application that operates on file input, it’s a solved problem. Grab AFL or some other all-in-one suite, hit go, and profit! |
Melissa Benua
|
|
Conquering the Testing Challenges of Serverless Applications[presentation]
Slideshow
Serverless cloud applications are becoming mainstream. Teams focus on developing and deploying code on a known technology stack and runtime, with fixed interfaces for application, database, and network, and they offer lower costs, faster development, and elastic growth. |
Peter Varhol
|
|
6 Steps for Succeeding with Test Automation in Agile[article] Lots of test automation efforts in agile software development fail, or at least do not maximize their potential. This article looks at two main reasons test automation may not live up to the expectations that testers and other stakeholders in the agile development process have, then outlines six steps to avoid falling into these traps. Here's how to succeed with test automation in an agile environment. |
||
How to Get Value from Measuring Agile Team Health Metrics[article] One common metric in agile measures team health or team happiness, but creating a way to measure this that is valued by the team is not an easy task. It’s having clarity on the reason you’re measuring these metrics and who benefits from it that gives you real value. Here are some ways you can measure this elusive quality, as well as how to make sure you're gaining useful information. |
||
5 Ways to Tackle Mobile Development Problems Early with Scrum[article] Using Scrum for mobile application development can be difficult due to various challenges inherent to building mobile applications. Environmental dependencies, platform limitations, service outages, ownership and access issues, and short sprints can all derail your agile development. Here are some tips for overcoming these five common mobile application development issues early by using Scrum. |
||
Conscious Curiosity: The Key To Innovation[presentation]
Slideshow
Jessie Shternshus shares her innate and learned curiosity, and how it fueled her exploration of the subject. She walks you through how she has learned to ask more inquisitive questions, looks for new and different ways to connect people, and connects the dots between ideas. |
Jessie Shternshus
|
|
The Lazy Student’s Guide to Test Automation[presentation]
Slideshow
Do you loathe regression? Do you tire of the repetitive tasks that are part of your product's lifecycle? If you do, then you might be lazy like Chris Loder. Since his Grade 4 teacher wrote “Chris is lazy” on his report card, it has become his way of life. |
Chris Loder
|
|
A Framework for the Whole Team to Own Quality[presentation]
Slideshow
In this practical and inspiring talk, Jess Ingrassellino will share how she developed collaborative test charters when she started working as the first exploratory tester at Salesforce.org. |
Dr. Jess Ingrassellino
|
|
The Agile Advantage for Last-Minute Changes[article] Companies using heavyweight development processes manage change by limiting or locking down scope, but this has negative consequences for our products and our customers. Agile takes a different approach by recognizing the value of last-minute changes and making it inexpensive and straightforward to make changes to software, even late in the development cycle, using continuous integration. |
||
Redefining the Project Manager Role in Scrum[article] Scrum teams are meant to become self-sustaining, so it’s natural for project managers to wonder how they will fit into this new environment. But they still have important skills. Their new role may—and probably will—look different from the traditional project manager role they’ve been used to, but there are still plenty of opportunities to provide real value to their new Scrum team. |
||
Marrying AI with Software Testing: An Interview with Wendy Siew Wen Chin and Heng Kar Lau[interview]
Video
In this interview, Wendy Siew Wen Chin and Heng Kar Lau, from Intel, discuss their STARWEST presentation, “Marrying Artificial Intelligence with Software Testing: Challenges and Opportunities.” They discuss their experiences with AI, their first STARWEST conference, and some of the differences they have observed between testing practices in Malaysia, their home country, and the United States. |
||
For Distributed Agile Teams, It’s Not All about the Tools[article] Many managers and distributed team members think that if they just had the right tools, they could make some agile approach work. Maybe, but tools only enhance the work of a collaborative agile team. Before you select tools, make sure you have people who can work together and have enough skills and capabilities for your distributed team. Tools do not make the team; they support the team. |
||
What Testers Can Learn from Airline Safety Improvements: An Interview with Peter Varhol and Gerie Owens[interview]
Video
Technologist and evangelist Peter Varhol and Gerie Owens, a test architect and certified ScrumMaster, discuss their STARWEST presentation, “What Aircrews Can Teach Testers about Testing.” They talk about how testers can apply airline safety practices to their teams’ delivery of high-quality applications through complementary expertise, collaboration, and decision-making. They also explain how blind deference to authority and automation can be detrimental to a testing team, and how to use everyone’s skills to achieve success. |
||
Build Just Enough of a Feature with ATDD[article] Developers have a tendency to overbuild their code. This is frequently due to not knowing exactly when they're done and not knowing how robust a feature needs to be. Acceptance test-driven development (ATDD) is a great way to avoid this practice because when the acceptance test passes, the developer knows they're done building that particular feature. |