0% found this document useful (0 votes)
51 views5 pages

Ste Final

The document discusses factors to consider when selecting a testing tool for test automation. It lists six key factors: i) assessing organizational maturity, ii) identifying areas for tool support, iii) evaluating tools against requirements, iv) proof-of-concept, v) evaluating the vendor, and vi) planning implementation.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
51 views5 pages

Ste Final

The document discusses factors to consider when selecting a testing tool for test automation. It lists six key factors: i) assessing organizational maturity, ii) identifying areas for tool support, iii) evaluating tools against requirements, iv) proof-of-concept, v) evaluating the vendor, and vi) planning implementation.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

Enlist 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).

State the testing approaches that are considered during client server testing

Testing approaches of client server system:

Component Testing: One need to define the approach and test plan for testing client and server
individually. When server is tested there is need of a client simulator, whereas testing client a server
simulator, and to test network both simulators are used at a time.

 Integration testing: After successful testing of server, client and network, they are brought together
to form system testing.

 Performance testing: System performance is tested when number of clients is communicating with
server at a time. Volume testing and stress testing may be used for testing, to test under maximum load
as well as normal load expected. Various interactions may be used for stress testing.

Concurrency Testing: It is very important testing for clientserver architecture. It may be possible that
multiple users may be accessing same record at a time, and concurrency testing is required to
understand the behavior of a system in this situation

State the need of automated testing tools

● 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.● 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.
Give the defect classification and its meaning.

Requirement/Specification Defects: Requirement-related defects arise in a product when one fails to


understand what the customer requires

Design Defects: Design defects occur when system components, interactions between system
components, interactions between the outside software/hardware, or users are incorrectly designed.

Coding Defects: This defect arises when variables are not initialized properly or variables are not
declared correctly or database is not created properly.

. Testing Defects: These would encompass incorrect, incomplete, missing inappropriate test cases and
test procedures.

State the Entry and Exit criteria’s for the software testing.

Entry criteria

Entry criteria are the condition or the set of conditions, which should exist or be met in order to start a
process.

Some of the conditions or situations, which may be seen as an entry criterion for the initiation of testing
activities. • Requirements should be clearly defined and approved. • Test Design and documentation
plan is ready. • Testers are trained, and necessary resources are available. • Availability of proper and
adequate test data (like test cases). • It depends upon which software development model is used.

Exit criteria

Exit Criteria is often viewed as a single document concluding the end of a life cycle phase. Some of the
conditions or situations which may be seen as an exit criterion for testing activities.

• Testing Deadline • Completion of test case execution. • Completion of Functional and code coverage
to a certain point. • Bug rates fall below a certain level and no high priority bugs are identified.

• Management decision

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 be presented.
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 opensource network of
support.

Explain how a test plan is prepared

The test plan acts as the anchor for the execution, tracking and reporting of the entire testing project
and covers.

Preparing test plan: What needs to be tested the scope of testing, including clear identification of what
will be the tested & what will not be tested.

How the testing is going to be performed breaking down the testing into small and manageable tasks
and identifying the strategies to be used for carrying out the tasks.

What resources are needed for testing- computer as well as human resources.

The time lines by which the testing activities will be performed. Risks that may be faced in all of the
above, with appropriate mitigation and contingency plans

Explain the process, how the bug is reported.

A bug report documents an anomaly discovered during testing. It includes all the information needed to
reproduce the problem, including the author, release/build number, open/close dates, problem area,
problem description, test environment, bug type, how it was detected, who detected it, priority,
severity, status, etc. After uncovering a bug, testers generate a formal bug report. The purpose of a bug
report is to state the problem as clearly as possible so that developers can replicate the bug easily and
fix it
Explain criteria to select testing tool

1. The tool must match its intended use. Wrong selection of a tool can lead to problems like lower
efficiency and effectiveness of testing may be lost.

2. Different phases of a life cycle have different quality-factor requirements. Tools required at each
stage may differ significantly.

3. Matching a tool with the skills of testers is also essential. If the testers do not have proper training
and skill then they may not be able to work effectively.

4. Select affordable tools. Cost and benefits of various tools must be compared before making final
decision.

5. Backdoor entry of tools must be prevented. Unauthorized entry results into failure of tool and creates
a negative environment for new tool introduction.

Explain when to start and stop testing.

Process model is a way to represent any given phase of software development that prevent and
minimize the delay between defect injection and defect detection/correction.

Entry criteria, specifies when that phase can be started also included the inputs for the phase.

Tasks or steps that need to be carried out in that phase, along with measurements that characterize the
tasks.

Verification, which specifies methods of checking that tasks have been carried out correctly. Clear entry
criteria make sure that a given phase does not start prematurely.

The verification for each phase helps to prevent defects. At least defects can be minimized. Exit criteria,
which stipulate the conditions under which one can consider the phases as done and included are the
outputs for the phase.

Exit criteria may include:

1. All test plans have been run 2. All requirements coverage has been achieved. 3. All severe bugs are
resolved.

Explain quality assurance and quality control

Quality Assurance: i. It is Process oriented activities. ii. A part of quality management focused on
providing confidence that quality requirements will be fulfilled.

Quality Control: i. It is Product oriented activities. ii. A part of quality management focused on fulfilling
quality requirements.
What is test plan? Write its two advantage.

-Test planning is the first activity of test team. If a tester does not plan for testing then it leads to failure.
Test plans are defined in framework created by test strategy and established by test policy 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. The test plan acts as the anchor for the execution,
tracking and reporting of the entire testing project and covers.

Advantages-

1.Work involved in test planning and setup pays in the long term. It gives insight testing activity
completely. One knows scope and deliverables of test plan execution.

2.Test plan describes the way in which testing team will show whether software work correctly as per
requirements and the acceptance criterial as defined b customer or development team with customer. It
defines various objectives for testing to measure its performance and coverage offered

State & explain any four benefits of automation in testing.

: Benefits of automation testing:

1. Speed: Think about how long it would take you to manually try a few thousand test cases for the
windows Calculator. You might average a test case every five seconds or so. Automation might be able
to run 10, 100 even 1000 times that fast.

2. Efficiency: While you are busy running test cases, you can’t be doing anything else. If you have a test
tool that reduces the time it takes for you to run your tests, you have more time for test planning and
thinking up new tests.

3. Accuracy and Precision: After trying a few hundred cases, your attention may reduce and you will
start to make mistakes .A test tool will perform the same test and check the result perfectly, each and
every time.

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

Describe any two special tests in testing process.

. Smoke Testing: is a testing technique that is inspired from hardware testing, which checks for the
smoke from the hardware components once the hardware's power is switched on. ii. In Software testing
context, smoke testing refers to testing the basic functionality of the build. iii. If the Test fails, build is
declared as unstable and it is NOT tested anymore until the smoke test of the build passes.

You might also like