In the software development life cycle, we find that testing is an important and integral part. Most people are of the view that testing phase can only be initiated for testing once the code is ready. They are wrong!!!
Testing will in fact be initiated from the requirements gathering phase until the stage when the product goes live. i.e. into production.
Let’s see the set of documents that aid testing during the various phases of software development.
With the onus on testing to deliver quality products, it became necessary to have a set of documents that are manageable and make sense to the development community. In comes various tools that will aid the testing and development community to track these documents. These tools manage all the testing activities and provide different kinds of reports.
Writing Test Cases for Security Test (Role Based).
What is a test case?
In software engineering, a product/ application is to be tested by exercising all possible combinations of features and inputs. In order to define a test case, we can say “It is a set of conditions or combination of variables under which a tester/ engineer will identify whether the application under test is working correctly or not”.
A single test case will not however verify that the application is working as desired. It will take numerous test cases for execution before we say that the application features are working correctly.
The typical set of test cases that are commonly used to test a particular application are