Project 1 - V&V SW Analysis - I
TEST PLAN:
A Test Plan refers to a detailed document that catalogs the test strategy, objectives, schedule, estimations, deadlines, and the resources required for completing that particular project.
if(owner long press the power button)
{
open the company logo at centre;
}
else if(customer press the power button)
{
open the apps in grid;
}
else if(owner power on the phone)
{
shows call the phone icon on first position at bottom;
}
else if(owner power on the phone)
{
shows Dictionary icon on second position at bottom;
}
else if( owner click on call the phone icon)
{
contacts appears in chronological order;
}
else if(owner click on Dictionary icon)
{
search bar appears at centre;
}
else if(owner long press power on button)
{
displays Good-Bye and gets switched off;
}
else if(owners phone font)
{
always in calibri with size of 12;
}
else if(customer requirement touch responsive)
{
reflects on touch;
}
else ( customer requirement no hard buttons)
{
touch screen sensitive;
}
TEST CASE TECHNIQUE:
1)Boundary Value Analysis (BVA):
BVA is another Black Box Test Design Technique, which is used to find the errors at boundaries of input domain (tests the behavior of a program at the input boundaries) rather than finding those errors in the centre of input. So, the basic idea in boundary value testing is to select input variable values at their: minimum, just above the minimum, just below the minimum, a nominal value, just below the maximum, maximum and just above the maximum. That is, for each range, there are two boundaries, the lower boundary (start of the range) and the upper boundary (end of the range) and the boundaries are the beginning and end of each valid partition. We should design test cases which exercise the program functionality at the boundaries, and with values just inside and outside the boundaries. Boundary value analysis is also a part of stress and negative testing.
Equivalence Class:
Equivalence partitioning is also known as “Equivalence Class Partitioning”. In this method, the input domain data is divided into different equivalence data classes – which are generally termed as ‘Valid’ and ‘Invalid’. The inputs to the software or system are divided into groups that are expected to exhibit similar behavior. Thus, it reduces the number of test cases to a finite list of testable test cases covering maximum possibilities.
2)Classification Tree Method:
The Classification Tree Method is a method for test design, as it is used in different areas of software development. It was developed by Grimm and Grochtmann in 1993. Classification Trees in terms of the Classification Tree Method must not be confused with decision trees.
3)Elementary Comparison Test:
The elementary comparison test ( ECT) is a thorough technique for the detailed testing of the functionality. The necessary test basis is pseudo-code or a comparable specification in which the decision points and functional paths are worked out in detail and structurally.
4)Control Flow Test:
Control flow testing is a testing technique that comes under white box testing. The aim of this technique is to determine the execution order of statements or instructions of the program through a control structure. The control structure of a program is used to develop a test case for the program.
5)Design Transition Technique:
State Transition Testing is a type of software testing which is performed to check the change in the state of the application under varying input. The condition of input passed is changed and the change in state is observed
6)Error Guessing:
Error guessing is a type of testing method in which prior experience in testing is used to uncover the defects in software. It is an experience based test technique in which the tester uses his/her past experience or intuition to gauge the problematic areas of a software application
TEST CASE ATTRIBUTES
- TestCaseId – A unique identifier of the test case.
It is a mandatory field that uniquely identifies a test case e.g. TC_01. - Test Summary– One-liner summary of the test case.
This is an optional field. Normally the test cases either have the ‘Test Summary’ field or the ‘Description’ field. - Description – Detailed description of the test case.
This field defines the purpose of the test case e.g. verify that the user can login with a valid username and valid password. - Prerequisite or pre-condition– A set of prerequisites that must be followed before executing the test steps.
For example – while testing the functionality of the application after login, we can have the pre-requisite field as “User should be logged in to the application”. - Test Steps– Detailed steps for performing the test case.
This is the most important field of a test case. The tester should aim to have clear and unambiguous steps in the test steps field so that some other person can follow the test steps during test execution. - Test Data– The value of the test data used in the test case.
For example – while testing the login functionality, the test data field can have the actual value of the username and password to be used during test execution. - Expected result– The expected result in order to pass the test.
Based on the test steps followed and the test data used, we come up with the expected result e.g. the user should successfully login and navigated to home page. - Actual result– The actual result after executing the test steps.
This field is filled during test execution only. In this field, we write the actual result observed during the test case execution. - Test Result– Pass/Fail status of the test execution.
Based on the expected result and the actual result, the test case is marked as passed or Failed.
Apart from Pass/Fail, we can have other values also like-
Deferred, when the test case is marked to be executed later, for some reason.
Blocked, when the test case execution is blocked due to some other issue in the application).
- Automation Status– Identifier of automation – whether the application is automated or not.
This is an optional field used only when we have automation in the project. - Date – The test execution date.
This field helps in keeping track of the different iteration during multiple test execution cycles. - Executed by– Name of the person executing the test case.
This field helps when there are multiple team members working on the test execution activity.
TESTING TYPE
Though there are different testing types in practice but, the two major categories are Functional and Non-functional types of testing.
Functional testing:
Functional testing is the process of validating functionality of a software application. Pass or fail is the result of a functional test, because either a feature works as designed or it does not.
The purpose of functional testing is to validate that the requirements of the software application have been met. It is important because functional testing assesses an application’s fitness to be released to end users. While software engineering has evolved in the past decade, functional testing remains a core part of quality testing.
Nonfunctional testing:
Nonfunctional testing is just as critical as functional testing. And because teams need to conduct a mix of different types of testing, you need to be doing both.
Nonfunctional testing makes applications more usable and more reliable. Unfortunately, it can often be rushed in an effort to meet release deadlines.
When nonfunctional testing is overlooked, performance and UX defects can leave users with a bad experience and cause brand damage. Worse, applications could crash with an influx of users. Accessibility defects can result in compliance fines. And their security could be at risk.
Black Box Testing
Black Box Testing is a software testing method in which the functionalities of software applications are tested without having knowledge of internal code structure, implementation details and internal paths. Black Box Testing mainly focuses on input and output of software applications and it is entirely based on software requirements and specifications. It is also known as Behavioral Testing.
White box testing ;
White box testing is an approach that allows testers to inspect and verify the inner workings of a software system—its code, infrastructure, and integrations with external systems.
Unit testing :
In computer programming, unit testing is a software testing method by which individual units of source code—sets of one or more computer program modules together with associated control data, usage procedures, and operating procedures—are tested to determine whether they are fit for use.
Integration testing:
Integration testing -- also known as integration and testing (I&T) -- is a type of software testing in which the different units, modules or components of a software application are tested as a combined entity. However, these modules may be coded by different programmers.