[go: up one dir, main page]
Scribd
Upload
53 views6 pages

Sta Test-Iv

Uploaded by

manikandan02.04.2003
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
53 views6 pages

Sta Test-Iv

Uploaded by

manikandan02.04.2003
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

DEPARTMENT OF INFORMATION TECHNOLOGY

SUBJECT:SOFTWARE TESTING AND AUTOMATION

YEAR:III SEM:VI SEC:A&B

PART-A

1. What is Test Design?


Test design is a process that defines how testing has to be done. It involves the
process of identifying the testing techniques, test scenarios, test cases, test data,
and expected test results.
Also, testers need to be specific about the test cases they create, such as
providing specific inputs, steps, and test data for each test case.

2.When to Create a Test Design?


Test design should be created once the test conditions are defined, and adequate
information is available to create the test cases of both high and low levels.
3.Define Resource Requirement
 Resource requirement is a detailed summary of all types of resources required to
complete project task. Resource could be human, equipment and materials
needed to complete a project.
 The resource requirement and planning is important factor of the test planning
because helps in determining the number of resources (employee, equipment…)
to be used for the project. Therefore, the Test Manager can make the correct
schedule & estimation for the project.
4. What is Tester Assignment?
 To access this page, click Execution Planning > Manual Execution Planning .
On the top right, click Test Assignment.
 The Test Assignment view is the second view of the Manual Execution
Planning page. Here you can organize the manual tests that are assigned to the
selected testing cycle
PART-B

1. Explain briefly about Test Design Factors?

These factors help testers create effective and efficient test designs that ensure
comprehensive coverage of the software under test and maximize the chances of
detecting defects.

Test design factors in software testing refer to the considerations and principles
that guide the creation of effective test cases and test suites. Here are some
important test design factors in detail :

Test objective: The test objective defines the purpose of testing and determines
the focus and scope of the testing effort. It includes goals such as finding
defects, verifying specific functionality, assessing performance, or ensuring
compliance with requirements.

Test coverage: It ensures that different aspects of the system, such as


functionality, inputs, outputs and error conditions, are adequately tested. Test
design should aim for maximum coverage within the available resources.

Test techniques: to design test cases Different techniques, such as equivalence


partitioning, boundary value analysis, decision table testing and state
transition testing, help identify representative test scenarios and ensure
effective coverage.

Test case prioritization: Prioritization is based on factors such as risk,


criticality and business impact. High-priority test cases, which cover critical
functionality or are likely to expose major defects, are executed earlier. Test
design should consider prioritization to ensure that critical areas are tested
early in the testing cycle.
Test data: Test data includes inputs, expected outputs and any other necessary
information required for test execution. Well-designed test data should cover a
range of valid and invalid scenarios, boundary conditions and corner cases.

Test environment: The test environment consists of the hardware, software


and network configurations required to execute tests. Test design should
consider the specific characteristics of the target environment, including
operating systems, browsers, databases and network setups.

Test maintainability: Test maintainability refers to the ease with which test
cases can be updated, reused and maintained over time. Test design should
consider factors such as test case documentation, reusability and test
automation to enhance maintainability.

Test automation: Test automation involves the use of tools and frameworks
to automate the execution of tests. Test design should identify suitable areas
for automation, such as repetitive or time-consuming tasks. Automated tests
should be designed with proper test structure, synchronization, error handling
and reporting mechanisms.

Test oracles: Test oracles are mechanisms used to determine the expected
outcomes of tests. Oracles can be specifications, requirements, historical data,
oracles derived from previous versions of the software, or expert judgment.

Test scalability: Test scalability refers to the ability of test cases and test suites
to handle increased workloads, larger datasets and higher complexity.

Test design factors are the factors that are considered when designing test cases.
These factors include the following:

Correctness: This is the minimum requirement of software. The tester may or


may not know the inside details of the software module under test (SMU) e.g.
control flow, data flow etc.
Negative: In this factor, we can check what the product is not supposed to do.
For example, if a login function is supposed to accept only valid usernames and
passwords.

• User interface: In UI testing, we check the user interfaces. This includes


checking the look and feel of the UI, as well as the functionality of the UL

Usability: This is the ease of use of the software. We can test usability by
asking users to try out the software and giving them feedback on how easy it is
to use.

Performance: This is the speed and responsiveness of the software. We can test
performance by running the software on different hardware configurations and
measuring the performance.

Security: This is the protection of the software from unauthorized access,


modification, or destruction.

Integration: This is the testing of how different components of the software


work together. For example, if we have a software that includes a web
application and a database,.

Reliability: This is the ability of the software to work correctly over time. We
can test reliability by running the software for a long period of time and
monitoring for errors.

Compatibility: This is the ability of the software to work with different


hardware and software platforms. We can test compatibility by running the
software on different platforms and checking for compatibility issues.

Here are some tips for considering text design factors

1. Start by identifying the specific requirements that need to be tested


2. Consider the risks associated with the software
3. Think about the different types of users who will be using the software
4. Consider the different environments in which the software will be used
5. Be realistic about the time and resources that are available for texting
6. Document the test design factors in the test plan
2. discuss briefly about test objective identification.

 Test objective identification in software testing refers to the process of


defining clear and specific goals for a testing effort. It involves determining
what aspects of the software or system need to be tested, what specific
functionalities should be validated and what quality attributes should be
evaluated.

 Test objective identification is the process of defining the specific goals that
a test case is intended to achieve. This is an important step in software
testing, as it helps to ensure that the test cases are targeted at the correct
areas of the software and that they are effective in finding defects.

Key steps involved in test objective identification may include:

Requirement analysis: Understanding the functional and non-functional


requirements of the software or system under test.

Risk assessment: Identifying potential risks and their impact on the software.
This includes evaluating the criticality of various functionalities and
determining which areas require more rigorous testing.

Defining testing goals: Establishing specific goals for the testing effort, such
as validating certain functionalities, ensuring system stability under load,
assessing performance metrics, or confirming compliance with industry
standards.

Prioritization: Determining the order of testing activities based on factors like


risk. importance, dependencies and project timelines.

Test scope definition : Clearly defining the boundaries of the testing effort,
including which components, modules, or functionalities will be covered and
which ones are out of scope.

Test coverage planning: Identifying the necessary test types, such as


functional, performance, security, usability, etc.,

Once the test objectives have been identified, they should be documented in the
test plan. This will help to ensure that the test cases are developed and executed
in a way that meets the specific goals of the testing.

Here are some of the benefits of test objective identification: .


1. It helps to ensure that the test cases are targeted at the correct areas of
the software.
2. It helps to ensure that the test cases are effective in finding defects.
3. It helps to improve the efficiency of the testing process.
4. It helps to ensure that the software meets the requirements.
Here are some tips for identifying test objectives:
1. Start by reviewing the software requirements.
2. Consider the risks associated with the software.
3. Think about the test environment.
4. Be specific and measurable.
5. Document the test objectives in the test plan.

You might also like