STAREAST | May 4–7, 2020 <br>#stareast

Blog

blog-banner

Conference Speaker

stack of product boxes
By Hans Buwalda | March 31, 2020
There's a case for treating some of your tests as products—project deliverables in their own right, created as a business investment. "Productizing" tests can show their value to management, but more importantly, it can help them contribute more effectively to the development lifecycle. Here are four steps to consider.
blog-banner

Conference Speaker

Crowd reflection toy
By Jeffery Payne | March 31, 2020
There’s an old saying that leadership is defined by what a leader does in a crisis. The current COVID-19 situation is such a crisis for every business. Whether you lead just yourself, a team, a line of business, or an enterprise, now is the time to step up and be a leader. Here's how to do that when times are tough.
blog-banner

Conference Speaker

Human-like robot with artificial intelligence
By Jason Arbon | February 14, 2020
Machine learning is rapidly growing more powerful, already sometimes imitating the actions and judgments of humans better than humans. In the near future, even before machines are conscious, they will be able to mimic human software testers. What will be the impact of AI on testing? Jason Arbon has a bunch of ideas.
blog-banner

Conference Speaker

three cucumbers
By Byron Katz | February 14, 2020
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.
blog-banner

Conference Speaker

Setting new trends
By Christine Fisher | January 24, 2020
Behavior-driven development is a methodology change that impacts the whole team, and unfortunately, it’s not as easy as writing scenarios in a specific format. What is the added value of BDD? Why should the team throw their current process out the window and try to incorporate a new methodology? Here are some reasons.