Related Content
Pushing System Performance with Stress Testing In performance testing, the term “stress” can have several possible meanings and can represent several different types of stress. Dale Perry details some common methods of stress testing when testing system performance. The key is knowing which stress tests make sense in your situation. |
||
Test Automation and When Enough Is Enough There are endless reasons why your test team might need to make use of automation. However, even if we’re at a point where most people agree you need some sort of test automation to compete in today’s agile landscape, using automation indiscriminately leads to more headaches than benefits. |
||
3 Benefits of Collecting User Feedback Early With agile software development, users are involved from the very beginning and are provided a minimum viable product to critique. A QA tool can be used to gather and organize user feedback while planning the next move. Sanjay Zalavadia highlights the benefits of collecting feedback early. |
||
Leverage Your Data to Establish Credibility as a Tester or Developer If you’re new to a team but have an important point to make during a meeting, it makes sense to just voice your opinion and get your message across, right? That’s easier said than done. It takes time to build credibility amongst your peers, so you need to back everything up with data. |
||
How to Future-Proof Yourself in the Testing Field The secret to making yourself invaluable as a tester isn’t learning how to see the future and forecast what will change the industry and what will fade away. In order to future-proof yourself, spend the time to add the skills you’re missing, and understand what might be coming on the horizon. |
||
Agile Demands a Holistic View of Testing and Automation Is your team struggling to transform your traditional testing methods, techniques, and tools in the context of an agile culture? The accountability for the right level of quality delivered at the right time belongs to the collective team. It's important to make decisions together about what value means. |
||
Changing the Narrative: Using Storytelling in Software Testing Stories change how we think and how we perceive our surroundings. This applies at work, too. What narrative did we tell ourselves during that project? Do we tell ourselves we are worthy of succeeding, or does our story tell us to fail again? Here are some ways testers can use stories to their advantage. |
||
Automation Can’t Work without a Proper Testing Strategy Simply saying, “Hey, make sure we have automated testing because that will fix everything” isn’t enough. If you don’t fully understand what needs to be automated, why it needs to be automated, and what tests should remain manual, you’re simply following fresh trends for the sake of looking relevant. |