system testing is testing done on a completely integrated system to know its compliance with the requirement.
Concurrency testing is done to see if two users use the application parallely how the application responds and how the data is handled.
Unit Testing is a testing done to check if the new code is working properly before delivering the build to testing team.
component testing is same as unit testing except for stubs and stimulators removed.
soak testing is a testing done to see how long the system can with stand with the no of users for a particular duration of time.
Feature Ref No.: Login page
Sub feature No.: N/A
Test case id: TC_01
Steps Description: Enter the valid user name and password
Pre condition: Application must accept the user name and
Input Criteria: username: abc, Password: ***
Expected Result: Login user page should open with all its
Severity: C1: High, C2: Normal, C3: Low
Observed Result: Application user page should open with all
There are basically two types of test cases:
@Positive test cases
@Negative Test cases
Test cases for mouse (few)
Mainly check mouse is attached system, color, check it buttons on it. etc
Adhoc testing is a negative testing, testing done with an unexpected situation or that 's not there in the requirement documents
Domain testing is the most frequently described test technique. Some authors write only about domain testing when they write about test design. The basic notion is that you take the huge space of possible tests of an individual variable and subdivide it into subsets that are (in some way) equivalent. Then you test a representative from each subset.
Smoke testing is testing the most important functionality without doing much deep into it when there's a new application delivered to testing team.
Load testing is done to know if the application can work normally under the defined number of user and if the response is alright even under that load
Test case is a detailed procedure that fully test a features or an aspect of a feature.
It describes how to perform a particular test. you need to develop a test case for each test listed in the test plan.
A test case includes:
gray box testing is the combination of unit testing and black box testing.
This is the very basic requirement to start with the testing phase. We should have the test cases for testing any system. test cases is written based on the scenarios you have to test the system. Test cases gives us the assurance that flows are working fine or not based on the status of the test case. If the status of some test cases are failed meaning some flows are not working fine and there is bug in the system that needs to be fixed. If the status of the test cases are passed meaning flow is working as expected and system is behaving as per the requirement.
Static checking is primarily the syntax checking or a manual review of the code.
Agile testing -testing using the agile model.
Security Testing is carried out in order to find out how well the system can protect itself from unauthorized access, hacking – cracking, any code damage etc. which deals with the code of application. This type of testing needs sophisticated testing techniques.
No software application can be written in a continuous mode of coding, at some point we need to branch out the code in order to perform a particular functionality. Branch coverage testing helps in validating of all the branches in the code and making sure that no branching leads to abnormal behavior of the application.
functional testing is a testing done on function by giving some input and expecting some output.
scalability testing is done to know how many extra users can use the application beyond the load specified.
According to me following things could be tested:
sanity testing is done after a new build to know if the important features are working properly .
Essentially a test case is a document that carries a Test Case ID no, title, type of test being conducted, Input, Action or Event to be performed, expected output and whether the Test Case has achieved the desired Output(Yes No).
Basically Test cases are based on the Test Plan, which includes each module and what to be tested in each module. Further each action in the module is further divided into testable components from where the Test Cases are derived.
Since the test case handles a single event at a time normally, as long as it reflects its relation to the Test plan, it can be called as a good test case. It does not matter whether the event passes or fails, as long as the component to be tested is addressed and can be related to in the Test Plan, the Test Case can be called a good Test Case.
Integration testing is testing done when we move from one screen to another screen or when two integrated modules are tested.
Ramp testing increases the no of user in a particular time frame to know tha max no of user that it can accommodate before throwing error messages.
Test case for telephone: