Test Planning

Articles

Requirements model Requirements Mapping Using Business Function Test Suites

On this team, testers were overcommitted, avoidable defects were surfacing, and documentation was hard to find. Worse, trust and morale were low. Upgrading tools was out of the question, so the testers decided to take matters into their own hands and create incremental change themselves. Here's how a team added a new type of traceability to its requirement test case world.

Balazs Schaffhauser
AngularJS logo Lessons Learned Testing Angular Applications

AngularJS is a framework used for organization of JavaScript code in highly interactive web and mobile applications. What does that mean from a testing perspective? Here's what should be in your test strategy when you’re testing Angular applications, including what might give you difficulty and how you can mitigate challenges.

Albert Gareev
Image of lock over code DevSecOps: Incorporate Security into DevOps to Reduce Software Risk

DevSecOps is a growing movement to incorporate security into DevOps practices in order to ensure flaws and weaknesses are exposed early on through monitoring, assessment, and analysis, so remediation can be implemented far earlier than traditional efforts. By failing fast with security testing, organizations reduce risk of a security incident and decrease the cost of rework.

Alan Crouch
Data servers 7 Steps to Improving Your Data Testing

When you have tens of thousands of rows of data, how do you know what to test or how much to test? A set percentage? Random test cases? When do you stop testing? It can be overwhelming. Here are seven steps to help your team streamline their data testing efforts and know what to test, how much to test, and when to stop testing.

Karis Van Valin
Weak link in a chain The Problem with How We Do Regression Testing

Current approaches to automated UI testing are broken because regression testing is not testing; regression testing is version control of the behavior of the system. The goal is functional consistency. The regression test ensures that, after a change to the software, the unchanged parts still work the same as before. This realization makes creating and maintaining tests much more efficient.

Jeremias Rößler
4 steps in a QA process 4 Strategies for a Structured QA Process

Being a software tester is no longer just about finding bugs. It is about continuous improvement, defining a clear test strategy, and going that extra mile to improve quality. Following a consistent, structured approach to QA will help you acquire more knowledge about the product you are testing, ask questions you otherwise may not have thought of, and become a true owner of quality.

Praveena Ramakrishnan
Bug taxonomy Using Bug Taxonomy to Design Better Software Tests

In software testing, bug taxonomy involves defining feature categories and collecting lists of possible bugs in each category. These lists can be used to give inexperienced testers some starting points, to help experienced testers brainstorm new ideas, and to evaluate the completeness of a test case. Using an existing bug taxonomy can be useful, but creating your own is even better.

Michael Stahl
Person looking at an app on multiple devices 3 Strategies for an Efficient Mobile App Testing Project

Developing a testing strategy for a mobile app means facing multiple challenges that are part of the field. But by employing these three strategies, you can get valuable feedback about your mobile app’s functionalities before it is published—while still keeping time and budget in mind.

Thomas Raynott
Tweezers plucking a password out of code Conducting Security Testing for Web Applications

As cyber attacks continue to create panic, the threat to our applications and data in the digital sphere grows stronger. Enterprises in the connected world need to realize that security testing is essential for their web applications. They need modern, all-inclusive security testing plans from the inception of their projects to ensure a secure user experience. Here's how to get started.

Ketan Sirigiri
Icon showing one end to another Endgame Testing: Exploring Your Agile Product End to End

The main goal of endgame testing is to test the system end to end from the user's perspective. This should ensure continuity between components developed by different teams, continuity in user experience, and successful integration of new features. Endgame testing will often identify gaps that are difficult to discover inside agile teams, including flows across the product.

Doron Bar

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.