1.

Write program for calculating even numbers from 1 to 20 And design

test cases for the same.

Program :

#include<stdio.h>
int main()
{
for(int i=0;i<=20;i=i+2)
{

printf("%d\n",i);
}
return 0;
}
2. State any eight limitations of manual testing.
1. Manual testing is slow and costly.
2. It is very labor intensive; it takes a long time to complete tests.
3. Manual tests don’t scale well. As the complexity of the software increases the
complexity of the testing problem grows exponentially. This leads to an increase in
total time devoted to testing as well as total cost of testing.
4. Manual testing is not consistent or repeatable. Variations in how the tests are
performed as inevitable, for various reasons. One tester may approach and perform
a certain test differently from another, resulting in different results on the same test,
because the tests are not being performed identically.
5. Lack of training is the common problem.
6. GUI objects size difference and color combinations are not easy to find in manual
testing. 7. Not suitable for large scale projects and time bound projects.
8. Batch testing is not possible, for each and every test execution Human user
interaction is mandatory.
9. Comparing large amount of data is impractical.
10. Processing change requests during software maintenance takes more time.
 3. Prepare defect report for login field of email application.

A defect report is a document that describes a defect, including its

severity, priority, and steps to replicate the problem.

• Defect id: D001

• Project Name: Web-Site Domain Name
• Module Name: Login
• Sub Module Name: User Login
• Type of Defect: Missing
• Status: New
• Severity: High
• Priority :
• Summary: User Login Page Not Opening
• Description : 1. Enter Url / Domain Name 2. Click On the User Login
Option
• Expected Result: User login page should get open
• Actual Results: User login page does not get open
• Reported By: ABC Tester
• Assign To: XYZ Developer
• Date & Time: 12/28/2022

4. State the need of automated testing tool.

Need for automated testing tools are:
• An automated testing tool can playback pre-recorded and predefined actions, compare
the results to the expected behavior and report the success or failure of these to a test
engineer.
• Once automated tests are created, they can easily be repeated, and they can be extended
to perform tasks impossible with manual testing.
• Automated Software Testing Saves Time and Money.
• Software tests must be repeated often during development cycles to ensure quality.

• Every time source code is modified software tests should be repeated. For each release of
the software, it may be tested on all supported operating systems and hardware
configurations. Manually repeating these tests is costly and time consuming.
• Once created, automated tests can be run repeatedly at no additional cost, and they are
much faster than manual tests.
• Testing Improves Accuracy, Even the most conscientious tester will make mistakes during
monotonous manual testing. Automated tests perform the same steps precisely every time
they are executed and never forget to record detailed results.
• They can even be run on multiple computers with different configurations.
• Automated software testing can look inside an application and see memory contents, data
tables, file contents, and internal program states to determine if the product is behaving as
expected.

5. Enlist different techniques for finding defects

Different techniques for finding defects are:

1. Static technique
2. Dynamic technique

3. Operational technique

6. Enlist any two activities involved in test planning.

1. Scope Management: Deciding what features to be tested and not to be tested.

2. Deciding Test approach /strategy: Which type of testing shall be done like
configuration, integration, localization etc.

3.Setting up criteria for testing: There must be clear entry and exit criteria for
different phases of testing. The test strategies for the various features and
combinations determined how these features and combinations would be tested.

4.Identifying responsibilities, staffing and training needs.

7. Design test cases for MS Word application using an Automation tool.

8. Which Parameters are considerd for writing good defect report
9. State the contents of ‘Test Summary Reports’ used in test reporting.

Test reporting is a means of achieving communication through the testing cycle.

There are 3 types of test reporting.
1. Test incident report
2. Test cycle report
3. Test summary report

Test summary Report:

The final step in a test cycle is to recommend the suitability of a product for release.
A report that summarizes the result of a test cycle is the test summary report.
There are two types of test summary report:
1. Phase wise test summary, which is produced at the end of every phase.
2. Final test summary report, which has all the details of testing done by all phases.

A Summary report should present :-

1. Test Summary Report Identifier
2. 2 Description: Identify the test items being reported in this report with test id
3. 3 Variances: Mention any deviation from test plans, test procedures, if any.
 4. 4 Summary of results: All the results are mentioned here with the resolved
incidents and their solutions.
5. 5 Comprehensive assessment and recommendation for release should include:
Fit for release assessment and recommendation of release.

10.Differentiate between static and dynamic testing tools.

11.Enlist any four benefits of test plan.

Need of test plan:
• Test Plan Ensures all Functional and Design Requirements are implemented as specified in
the documentation.
• To provide a procedure for Unit and System Testing.

• To identify the documentation process for Unit and System Testing.

• To identify the test methods for Unit and System Testing.
12. Enlist different types of defect classification.

Different types of defect classification are-

• Severity wise
• Work Product wise
• Type of error wise
• Status wise

13.Write any two root causes of defect.

Root causes of defect are:

i. Miscommunication of requirements introduces error in code.
ii. Lack of design Experience.
iii. Lack of coding practice.
iv. Unrealistic time schedule for development.
v. Multiple changes in the requirements.

14.Enlist the factors considered for selecting a testing tool for test
automation.
The following factors are important during tool selection:
i. Assessment of the organization’s maturity (e.g., readiness for
change).
ii. Identification of the areas within the organization where tool
support will help to improve testing processes.
iii. Evaluation of tools against clear requirements and objective criteria.
iv. Proof-of-concept to see whether the product works as desired and
meets the requirements and objectives defined for it.
v. Evaluation of the vendor (training, support and other commercial
aspects) or open source network of support.
vi. Identifying and planning internal implementation (including coaching
and mentoring for those new to the use of the tool).