Related Content
 |
The Cost of Software Testing Testing is regarded as the number one bottleneck in the software delivery process. Most people simply conclude that developers are value centers, and testers are cost centers. But developers' work also brings cost, and—more importantly—testers' work also brings value. It's time to reframe our thinking about testing. |
|
 |
A New Approach to Load Testing with Browser-Level Users Since the inception of load testing, the approach has been mostly the same: simulate the traffic of an application by creating load at the API level. But there have been market shifts that make load testing with browser-level users more feasible—allowing us to test with real load and measure true user performance. |
|
 |
Continuous Testing Is Not Automation Many people confuse continuous testing with test automation. That makes sense, because you cannot do continuous testing without automated tests. But it is much more. Continuous testing has a higher-level maturity that could require a totally different way of working—but it also gives a faster path to production. |
|
 |
Lessons Learned (and Unlearned) at STARCANADA 2018 With a week full of sessions, tutorials, training classes, and events, the STARCANADA software testing conference had plenty of takeaways. Some highlights: what jobs will look like in the future with AI, why testers should lead efforts to make quality everyone's responsibility, and the importance of unlearning. |
|
 |
How Are You Managing Your Test Debt? Just as debt can be good and bad in everyday life (such as a home mortgage), debt in the engineering world can also be good and bad. This applies to quality engineering as well—with good and bad test debt. As testers, how do we create a balance and stay at the right test-debt quotient? |
|
 |
4 Lessons from the STARWEST 2018 Keynote Presentations With a week full of sessions, tutorials, training classes, and events, the STARWEST software testing conference had plenty of takeaways useful for your professional and personal life. Here are four lessons distilled from the conference’s keynote presentations on testing, communication, and directing your career. |
|
 |
Code Katas for Testers A kata is a small programming task you build a solution to. The point is to develop programming skill through familiarity with programming patterns, which is a useful practice for testers today. You’ll learn about software development, testing, continuous integration, exploration—and even how to be a better person. |
|
 |
Writing Tests: Action Abstraction Keywords have become a popular way of writing tests. Hans Buwalda used keywords to devise the Action Based Testing method in which tests are written as sequences of “actions” represented with keywords. However, keywords are just a physical representation of actions, and there are other ways to do this. |
