Test Case Writing & Improving Productivity – Neotys Testing Roundup

1. How to Prepare Yourself For Test Case Writing and Improve Your Productivity

For any tester, writing high quality test cases is (or should be) a top priority. In order to improve the efficiency and productivity of test case writing, testers should be aware of a few key points.

First comes professional and psychological preparation. Then testers will need to identify and understand the quality metrics involved in the project. Finally, testers will need to know how bugs are reported, how issues are escalated and how the test reports are prepared for stakeholders.

This post from Software Testing Help dives into each of these points and provides a solid outline for testers looking to improve this process. Take a look.

2. Managing Security Testing in Agile Software Development

When it comes to agile software development, it’s often easy to push tasks to the side with the simple excuse of not having enough time. We get it; things move fast. However, there are certain activities that must be performed in order to ensure application quality and security.

Take security testing, for example. One of the biggest myths in the world of agile development is that there is not enough time during each sprint to do security testing. These days, application security is of the upmost importance and cannot be overlooked.

Read this full article to discover why your organization should perform security testing and to brush up on some tips for introducing security testing into your agile environment.

3. How Testers Can Add Value Earlier in the Development Lifecycle

Despite popular opinion, continuous integration (CI) isn’t just for developers—testers also play their own important roles. Still, testers can often feel forgotten or unsure about how they fit into the CI lifecycle.

So, how do you start when you are dropped into a team that practices continuous integration? Ultimately, working together with the entire team is key to increasing application quality early on. But keep in mind, adding value to the development lifecycle isn’t solely for environments where continuous integration is implemented.

To explore solutions that will help you add value to the development lifecycle—whether you work in an agile, DevOps, or traditional context—view the full article here.

4. Discussion: How important is [it] for a tester to know the characteristics of a product?

After working on different projects and speaking with others at various software testing events, Alin Groza noticed a difference in the way testers approach product knowledge.

He describes two common, general approaches. In the first, testers are involved in a large number of testing activities and ensure that they have a good knowledge of the product that is developed and tested within the project. The second approach is often used by testers who focus on automation rather than product characteristics. These testers don’t necessarily want to know everything about a single product or spend all their time testing it.

So what are your thoughts on the topic? What approach do you use when it comes to product knowledge? Contribute your response here.

Leave a Reply

Your email address will not be published. Required fields are marked *