Ans-1

Ans-2

1. Save Time /Speed: Due to advanced computing facilities, automation test tools prevail in

speed of processing the tests. Automation saves time as software can execute test cases faster

than human.

2. Reduces the tester’s involvement in executing tests: It relieves the testers to do some

other work.

3. Repeatability/Consistency: The same tests can be re-run in exactly the same manner

eliminating the risk of human errors such as testers forgetting their exact actions,

intentionally omitting steps from the test scripts, missing out steps from the test script, all of

which can result in either defects not being identified or the reporting

of invalid bugs (which can again, be time consuming for both developers and testers to

reproduce)

4. Simulated Testing: Automated tools can create many concurrent virtual users/data and

effectively test the project in the test environment before releasing the product.

5. Test case design: Automated tools can be used to design test cases also. Through

automation, better coverage can be guaranteed than if done manually.

6. Reusable: The automated tests can be reused on different versions of the software, even if
the interface changes.

7. Avoids human mistakes: Manually executing the test cases may incorporate errors. But

this can be avoided in automation testing.

9. Cost Reduction: If testing time increases cost of the software also increases. Due to

testing tools time and therefore cost is reduced.

10. Relentlessness: Test tool and automation never tire or give up. It will continuously test

the software.

Ans-3

1) Proficiency is required to write the automation test scripts.

2) Debugging the test script is major issue. If any error is present in the test script, sometimes

it may lead to deadly consequences.

3) Test maintenance is costly in case of playback methods. Even though a minor change

occurs in the GUI, the test script has to be re-recorded or replaced by a new test script.

4) Maintenance of test data files is difficult, if the test script tests more screens.

Ans-4
Ans-5
Test ID Test Objective Prerequisite Steps Input Data Expected Results Actual Results Status

TC-1 verify the addition Calculator Enter 1st operand Enter 2 + 2 4 4 pass
operation Should be '+' operator Enter 2nd
Working operand

TC-2 verify the addition Calculator Enter 1st operand Enter (-2 )+( -2) 0 0 pass
operation Should be '+' operator Enter 2nd
Working operand
TC-3 verify the Calculator Enter 2 Negative number (-3) - (-5) - 4 -2 -2 pass
subtration Should be and 1 positive number to
operation Working perform subtraction

TC-4 verify the Calculator Select log operation Enter log2(8) 3 3 pass
logarithmic Should be theta value
operation Working
TC-5 verify the sin Calculator Select sin operation Enter sin (90) 1 1 pass
operation Should be theta value
Working
TC-6 verify the cos Calculator Select cos operation Enter cos(90) 0 0 pass
operation Should be theta value
Working
TC-7 verify the tan Calculator Select tan operation Enter tan(90) undefined undefined pass
operation Should be theta value
Working
TC-8 verify the cosec Calculator Select cosec operation cosec(90) 1 1 pass
operation Should be Enter theta value
Working

Ans-6

Enlist any six attributes of defect. Describe them with suitable example.

Defect has following attributes:

Any six of the following attributes shall be considered

1) Defect ID: Identifies defect as there are many defects might identified in system.

a. i.e. D1, D2, etc.

2) Defect Name: Name of defect which explains the defect in brief.

a. It must be short but descriptive. i.e. Login error.

3) Project Name: Indicates project name in which defect is found

4) Module /Sub-module name: for which the defect is found.

5) Phase introduced: Phase of life cycle to which the defect belongs to.

6) Phase found: Phase of project when the defect is found is added here. It is used to find defect

leakage or stage.

7) Defect type: Defines defect type. i.e. security defect, functional defect, GUI defect etc.

8) Severity: Declared in test plan, i.e. high medium or low.

9) Priority: defines on the basis of how the project decides a schedule to take the defects for

fixing.
10) Summary: Describes short about the defect.

11) Description: Describes it in detail.

12) Status: dynamic field, open, assigned, resolved, closed, hold, deferred, or reopened, etc.

13) Reported by/ Reported on: Who found defect, and on what date.

Ans-7

Limitations of Manual Testing:

• Manual Testing requires more time or more resources, sometimes both.

• Performance testing is impractical in manual testing.

• Less Accuracy

• Executing same tests again and again time taking process as well as Tedious.

• GUI Objects Size difference and Color combinations etc..Are not easy to find in Manual

Testing.

• Not Suitable for Large scale projects and time bounded projects.

• Batch Testing is not possible, for each and every test execution Human user interaction is

mandatory.

• Manual Test Case scope is very limited, if it is Automated test, scope is unlimited.

• Comparing large amount of data is impractical

• Checking relevance of search of operation is difficult

• Processing change requests during software maintenance takes more time

Ans-8

The different states of a bug in the bug life cycle are as follows:

New: When a tester finds a new defect. He should provide a proper Defect document to the

Development team to reproduce and fix the defect. In this state, the status of the defect posted by

tester is “New”

Assigned: Defects which are in the status of New will be approved (if valid) and assigned to the

development team by Test Lead/Project Lead/Project Manager. Once the defect is assigned then

the status of the bug changes to “Assigned”

Fixed: When a developer makes the necessary code change and verifies the change, then the

status of the bug will be changed as “Fixed” and the bug is passed to the testing team.

Test: If the status is “Test”, it means the defect is fixed and ready to do test whether it
is fixed or not.

Verified: The tester re-tests the bug after it got fixed by the developer. If there is no

bug detected in the software, then the bug is fixed and the status assigned is

“verified.”

Closed: After verified the fix, if the bug is no longer exits then the status of bug will

be assigned as “Closed.”

Reopen: If the defect remains same after the retest, then the tester posts the defect

using defect retesting document and changes the status to “Reopen”. Again the bug

goes through the life cycle to be fixed.

Duplicate: If the defect is repeated twice or the defect corresponds the same concept

of the bug, the status is changed to “duplicate” by the development team.

Deferred: In some cases, Project Manager/Lead may set the bug status as deferred.

If the bug found during end of release and the bug is minor or not important to fix

immediately

If the bug is not related to current build

If it is expected to get fixed in the next release

Customer is thinking to change the requirement

In such cases the status will be changed as “deferred” and it will be fixed in the next

release.

Rejected: If the system is working according to specifications and bug is just due to

some misinterpretation (such as referring to old requirements or extra features) then

Team lead or developers can mark such bugs as “Rejected”

Ans-9

Test Planning: Like any project, the testing also should be driven by a plan. The test plan

acts as the anchor for the execution, tracking and reporting of the entire testing project.

Activities of test plan:

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

Ans-10
Ans-11
Ans-12
Ans-13

Refer to this test cases only…

Ans-14