Kavithavcet.files.wordpress.com



UNIT – 1

1. Define process.

Process, in the software engineering domain, is the set of methods, practices, standards, documents, activities, policies, and procedures that software engineers use to develop and maintain a software system and its associated artifacts, such as project and test plans, design documents, code and manuals.

2. Define Validation.

Validation is the process of evaluating a software system or component during, or at the end of, the development cycle in order to determine whether it satisfies specified requirements.

3. Define Verification.

Verification is the process of evaluating a software system or component to determine whether the product of a given development phase satisfy the conditions imposed at the start of that phase.

4. Define Testing.

Testing is generally described as a group of procedures carried out to evaluate some aspects of a piece of software.

(OR)

Testing can be described as a process used for revealing defects in software, and for establishing that the software has attained a specified degree of quality with respect to selected attributes.

5. Define Debugging.

Debugging, or fault localization is the process of

Locating the fault or defect.

Repairing the codes.

Retesting the code.

6. List out the levels of the testing maturity model..

Level 1: Initial.

Level 2: Phase Definition.

Level 3: Integration.

Level 4: Management and Measurement.

Level 5: Optimization/Defect prevention and quality control.

7. Define Errors.

An error is a mistake, misconception, or misunderstanding on the part of a software developer.

8. Define Faults.

A fault (defect) is introduced into the software as the result of an error. It is an anomaly in the software that may cause it to behave incorrectly, and not according to its specification.

9. Define Failures.

A failure is the inability of a software system or component to perform its required functions within specified performance requirements.

10. Define Test case.

A test case in the practical sense is a test- related item which contain the following information:

• A set of test inputs.

• Execution conditions.

• Expected outputs.

11. Define Test.

A test is a group of related test cases, or a group of related test cases and test procedures.

12. Define Test Oracle.

A test oracle is a document, or piece of software that allows tester to determine whether a test has been passed or failed.

13. Define Test Bed.

A test bed is an environment that contains all the hardware and software needed to test a software component or a software system.

14. Define Quality.

Two concise definitions for quality.

✓ Quality relates to the degree to which a system, system component, or process meets specified requirements.

✓ Quality relates to the degree to which a system, system component, or process meets customer or user needs, or expectations.

15. Define Metric.

A metric is a quantitative measure of the degree to which a system, system component, or process possesses a given attribute.

16. Define Quality Metric.

A quality metric is a quantitative measure of the degree to which an item possesses a quality attribute.

17. Define SQA.

The software quality assurance (SQA) group is a team of people with the necessary training and skills to ensure that all necessary actions are taken during the development process so that the resulting software conforms to established technical requirements.

18. Define Review.

A review is a group meeting whose purpose is to evaluate artifact or a set of software artifacts.

19. Define Precondition.

A precondition is a condition that must be true in order for a software component to operate properly.

20. Define Post condition.

A post condition is a condition that must be true when a software component completes its operation properly.

21. Compare Testing and debugging.

Testing and debugging, or fault localization, are two very different activities. The debugging process begins after testing has been carried out and the tester has noted that the software is not behaving as specified.

Testing: To determine if a code contains errors.

Debugging: To locate the error and fix it.

22. Define reviews.

A review is a group meeting whose purpose is to evaluate a software artifact or a set of Software artifacts. Review and audit is usually conducted by a SQA group.

23. Programmer A and Programmer B are working on a group of interfacing modules. Programmer A tends to be a poor communicator and does not get along well with Programmer B. Due to this situation, what types of defects are likely to surface in these interfacing modules?

Communication defects.

24. What is Test harness?

In software testing, a test harness or automated test framework is a collection of software and test data configured to test a program unit by running it under varying conditions and monitoring its behavior and outputs. It has two main parts: the test execution engine and the test script repository.

25. Short notes on Test script?

A test script in software testing is a set of instructions that will be performed on the system under test to test that the system functions as expected.

There are various means for executing test scripts.

Manual testing. These are more commonly called test cases.

Automated testing

Short program written in a programming language used to test part of the functionality of a software system. Test scripts written as a short program can either be written using a special automated functional GUI test tool (such as HP Quick Test Professional, Borland SilkTest, IBM TPNS and Rational Robot) or in a well-known programming language (such as C++, C#, Tcl, Expect, Java, PHP, Perl, Powershell, Python, or Ruby).

Descriptive Questions

1. Discuss in detail about Software testing principles.( AU June -2018)

2. Explain in detail the tester’s role in a software development organization

3. Explain in detail defect classes, the defect repository and test design

4. Identify the different types of defects occurred in software life cycle model and discuss the same with a suitable example.

5. Apply the knowledge of software testing principles to test attendance automation software.

6. Write short notes on origin of defects. Describe about tester support for developing defect repository. (AU – June 2018)

7. a) Explain in detail the tester’s role in a software development organization.

(b) Identify any four Testing axioms and explain in detail.

Course In-charge Module Coordinator HOD/IT

Dr. R. Kavitha Dr. R. Kavitha Dr. Perumalraja

UNIT – 2

1. List the two basic Testing strategies.

✓ Black box testing.

✓ White box testing.

2. What are the knowledge sources for Black box testing?

✓ Requirements

✓ Document specification

✓ Domain knowledge

✓ Defect analysis data

⎫

3. What are the knowledge sources for White box testing?

✓ High level design

✓ Detailed design

✓ Control flow graphs

✓ Cyclomatic complexity

4. List the methods of Black box testing.

✓ Equivalence class partitioning

✓ Boundary value analysis

✓ State transition testing

✓ Cause and effect graphing

✓ Error guessing

5. List the methods of White box testing.

✓ Statement testing

✓ Branch testing

✓ Path testing

✓ Data flow testing

6. Define Random testing

Each software system or module has an input domain from which test input data is selected. If a tester randomly selects input from the domain, this is called Random testing.

7. Define Equivalence class partitioning.

If a tester is viewing the software-under-test as a black box with well defined inputs and outputs, a good approach to selecting test inputs is to use a method called Equivalence class partitioning.

8. List the advantages of Equivalence class partitioning.

o It eliminates the need for exhaustive testing, which is not feasible.

o It guides a tester in selecting a subset of test inputs with a high probability of detecting a defect.

o It allows a tester to cover a larger domain of inputs/outputs with a smaller subset selected from an Equivalence class.

9. Define Cause effect graphing.

It is a technique that can be used to combine conditions and derive an effective set of test cases that may disclose inconsistencies in a specification.

10. Define State.

A state is an internal configuration of a system or component. It is defined in terms of values assumed at a particular time for the variables that characterize the system or component.

11. Define Finite-state machine.

It is an abstract machine that can be represented by a state graph having a finite number of states and a finite number of transitions between states.

12. What is Certification?

Certification refers to third-party assurance that a product, process, or service meets a specific set of requirements.

13. What is Test data set?

A test data set is statement, or branch, adequate if a test set T for program P causes all the statements, or branches, to be executed respectively.

14. Define Path.

A path is a sequence of control flow nodes usually beginning from the entry node of a graph through to the exit node.

15. Define Variable.

Variable is defined in a statement when its value is assigned or changed.

(OR)

Variable is defined in a statement when its value is utilized in a statement. The value of the variable is not changed.

16. Define Error guessing.

Error guessing approach is based on the testers/developers past experience with code similar to code-under-test, and their intuition as to where defects may lurk in the code.

17. What is the goal of smart tester?

The goal of the smart tester is to understand the functionality, input/output domain, and the environment of use for the code being tested.

18. What is boundary value analysis?

Boundary value analysis is useful to generate test cases when the input data is made up of clearly identifiable boundaries or ranges.

19. What is compatibility testing?

• Testing done to ensure that the product features work consistently with different infrastructure components is called compatibility testing.

• Actually Test case results not only depend on the product for proper functioning, they depend equally on the infrastructure for delivering functionality.

20. Summarize user documentation testing.

• User documentation covers all the manuals, user guides, installation guides, setup guides, read me file, software release notes and online help that are provided along with the software to help the end user to understand the software system.

• U.D is done to ensure the Documentation matches the product.

21. Why user documentation testing?

• To check if what is stated in the document is available in the product.

• To check if what is there in the product is explained correctly in the document.

22. Compare black box, white box and domain testing. ( AU JUNE 2018)

• White box testing – Checking code

• Black Box testing – Checking functionality without coding knowledge. ( Checking will be done by looking the specifications )

• Domain testing – Do not look the specification- Purely based on domain knowledge.

• It requires critical understanding of day-to-day business activities.

23. Give the schematic diagram of different types of testing.

[pic]

24. What is static testing?

• Requires only source code product, not the binaries or executable

• Static testing does not involve executing the programs on computers but involves select people going through the code to find

1. Whether cod works according to functional requirements.

2. The code has been written in accordance with the design developed earlier in the project life cycle.

3. Any functionality has been missed out

4. Code handles errors properly.

25. List out the different types of static testing.

Types

1. Desk checking

2. Code Walkthrough

3. Code review

4. Code inspection

26. What is desk checking?

• Done manually by author of the code

• Verification of the code is done for its correctness

• Verification by comparing the code with specification

• Process over before the compilation and execution of the code

27. What is walkthrough?

• Walkthrough are less formal than inspection

• Group oriented method

• Set of people look at the program code, and Raise the questions for the author

• Author should answer the questions.

28. Summarize code inspection.

It detects all faults, violations and other side effects. It is started after desk checking and walkthrough

Four roles in Inspections

1. Author of the code

2. Moderator – Formally run the inspection according to the process

3. Inspectors – Provide review comments on the code

4. Scribe – takes detailed notes during inspection meeting and circulates them to the inspection team after meeting

29. What is structural testing?

Structural testing is based on Code, Code structure and internal design. Structural testing runs by computer on the built product.

30. Summarize about program prime.

A program prime is an atomic programming unit. All structured programs can be built from three basic primes-sequential (e.g., assignment statements), decision (e.g., if/then/else statements), and iterative (e.g., while, for loops).

31. Short notes on path.

• A path is a sequence of control flow nodes usually beginning from the entry node of a graph through to the exit node.

• A path may go through a given segment of the control flow graph one or more times.

• For example, Path ---- 1-2-3-4-8 where the dashes represent edges between two nodes.

• For example, the sequence “4-8” represents the edge between nodes 4 and 8.

• Cyclomatic complexity “independent paths” in the graph.

• The independent paths are defined as any new path through the graph that introduces a new edge that has not be traversed before the path is defined.

32. What is error guessing?

• Error guessing is a test case design technique where the tester has to guess what faults might occur and to design the tests to represent them.

• Previous testing knowledge – Helpful for current testing

33. What is COTS components? ( AU JUNE 2018)

Commercial-off-the-shelf components. This term is used to refer to deployable units of software that offer a predefined set of services and are made available to consumers in a packaged form by vendors.

Descriptive Questions

1. Identify the test cases for the lock and key and assume that the lock requires two keys to be inserted in a particular order to unlock the locker. Construct RTM.

2. Build the Decision table consists of test cases and discusses the same for Income tax deduction calculation.

3. Identify the test cases for positive and negative testing and discuss the same with a suitable example.

4. Identify the test cases for testing one rupee telephone coin box.

5. Identify the test cases for cause and effect technique and discuss the same with a suitable example.

6. Select the suitable type of testing to test the internal components of the software and also explain cycloramic complexity value which is useful for identifying the number of test cases.

7. Apply the concept of “minimal test cases and maximum test coverage” in any scenario and draw cause and effect graph.

8. Apply Compatibility testing technique to find the test cases for real time application.

9. Explain in detail about the Equivalence class partitioning with an example. (AU June 2018)

10. Discuss the various approaches in Black Box test design.

11. Describe the difference between the white box and black box testing strategies.

12. What is a control flow graph? How is it used in white box test design?

13. Explain the differences between random testing and testing using error guessing.

14. Explain in detail about the Boundary Value analysis with an example. (AU June 2018)

15. Discuss in detail about static testing and structural testing. And also write difference between these testing concepts. (AU June 2018)

16. Plan test cases by giving suitable examples for structural testing.

17. Demonstrate McCabe’s Cyclomatic Complexity and find the cyclomatic complexity value (using Edges, nodes and independent path ) for the following code.

. [pic]

18. Write about program prime. Show the control flow graph for any code

19. Select any one scenario and write atleast eight test cases.

1 ) Checking the function of Mobile phone 2) Checking the function of Computer mouse.

20. Identify the test cases for the lock and key and assume that the lock requires two keys to be inserted in a particular order to unlock the locker. Construct RTM.

21. A sample rule for creating a table in SQL database is

CREATE TABLE table name (column1 data type, column2 data type.....);

For the above format the additional rules for constructing table is : Each of the keywords can be abbreviated to 3 characters or more. The column must be unique.

Construct state graph to derive the initial test cases for the above set of requirements

22. Construct Decision Table (with atleast five test cases) for the following scenario. (Uploading photo)

Now consider a dialogue box which will ask the user to upload photo with certain conditions like

1. You can upload only '.jpg' format image

2. File size less than 32kb

3. Resolution 137*177.

If any of the conditions fails the system will throw corresponding error message stating the issue and if all conditions are met photo will be updated successfully

Course In-charge Module Coordinator HOD/IT

Dr. R. Kavitha Dr. R. Kavitha Dr. Perumalraja

UNIT – 3

1. List the different levels of testing. (AU JUNE 2018)

✓ Unit test

✓ Integration test

✓ System test

✓ Acceptance test.

2. Define Unit Testing

A unit is the smallest possible testable software component that can be characterized in several ways.

3. List the components suitable for unit test.

✓ Procedures and functions

✓ Classes/objects and methods

✓ Procedure-sized reusable components.

4. List the phases in the unit test planning.

To prepare for unit test the developer/tester must perform several tasks. These are:

(i) Plan the general approach to unit testing;

(ii) Design the test cases, and test procedures (these will be attached to the test plan);

(iii) Define relationships between the tests;

(iv) Prepare the auxiliary code necessary for unit test.

5. What is Test harness?

The auxiliary code developed to support to testing of units and components is called a test harness. The harness consists of drivers that call the target code and stubs that represent modules it calls.

6. Differentiate alpha and beta test.

• Alpha tests bring potential users to the developer’s site to use the software. Developers note any problems.

• Beta tests send the software out to potential users who use it under real-world conditions and report defects to the developing organization.

7. Define Stub

Stubs are dummy modules which are known as "called programs" which is used in

integration testing (top down approach), used when sub programs are under construction.

8. Define Driver

Drivers are also kind of dummy modules which are known as "calling programs", which

is used in bottom up integration testing, used when main programs are under construction.

Stub means a Dummy model of a particular module.

9. List out the process in Process in Test Specification

Step 1 - Make it Run

Step 2 - Positive Testing

Step 3 - Negative Testing

Step 4 - Special Considerations

Step 5 - Coverage Tests

Step 6 - Coverage Completion

10. Summarize about test case design techniques

• Test case design techniques can be broadly split into two main categories.

• Black box techniques use the interface to a unit and a description of functionality, but do not need to know how the inside of a unit is built.

• White box techniques make use of information about how the inside of a unit works.

• There are also some other techniques which do not fit into either of the above categories. Error guessing falls into this category.

11. List out the goals of integration test.

Goals

Integration test for procedural code has two major goals:

o to detect defects that occur on the interfaces of units;

o to assemble the individual units into working subsystems and finally a complete system that is ready for system test.

12. What is the advantage of Bottom up integration?

Bottom-up integration has the advantage that the lower-level modules are usually well tested early in the integration process. This is important if these modules are candidates for reuse.

13.What is a cluster?

A cluster consists of classes that are related, for example, they may work together to support a required functionality for the complete system.

14.List the several types of system tests.

✓ Functional testing

✓ Performance testing

✓ Stress testing

✓ Configuration testing

✓ Security testing

✓ Recovery testing

15. Define Load.

A load is a series of inputs that simulates a group of transactions.

16. List the two major requirements of Performance testing.

✓ Functional requirements

✓ Quality requirements.

17.What is meant by Stress testing?

When a system is tested with a load that causes it to allocate its resources in maximum amounts, this is called stress testing.

18. Give the examples of security testing.

✓ Password checking

✓ Legal and illegal entry with password

✓ Password Expiration

✓ Encryption

✓ Browsing

✓ Trap doors

✓ Viruses.

19. Define Recovery testing.

Recovery testing subjects a system to losses of resources in order to determine if it can recover properly from these losses.

20. List the areas covered during recovery testing.

✓ Restart

✓ Switchover.

21. Define Use case.

A use case is a pattern, scenario, or exemplar of usage. It describes a typical interaction between the software system under development and a user.

22. Define Regression testing.( AU JUNE 2018)

Regression testing is not a level of testing, but it is the retesting of the software that occurs when the changes are made to ensure that the new version of the software has retained the capabilities of the old version and that has no defect have been introduced due to the changes.

23. List the objectives of configuration testing.

✓ Show that all the configuration changing commands and menus work properly

✓ Show that all interchangeable devices are really interchangeable, and that they each enter the proper states for the specified conditions

✓ Show that the system’s performance level is maintained when devices are interchanged, or when they fail.

24. List the effect of security breaches.

✓ Loss of information

✓ Corruption of information

✓ Misinformation

✓ Privacy violations

✓ Denial of service.

Descriptive Questions

1. State unit test and describe about planning and designing of unit test.(AU JUNE 2018)

2. Explain elaborately about the various types of system testing. (AU JUNE 2018)

3. How would you define a software unit? In terms of your definition, what constitutes a unit for procedural code; for object-oriented code?

4. Select the suitable method of testing to check the system after changes such as enhancement and discuss the same in detail.

5. Describe the activities/Tasks and responsibilities for developer/testers in support of multilevel testing.

6. Write the organizational approaches of unit testing. Sketch the different approaches and explain in detail.

7. Select the one from the following test scenarios would you subject to stress tests? Justify your answer.

Students logging on to find results of examinations on the net on the result day

8. Select the priority P0/P1/P2 for the following suggestions and justify your answer:

a. A test cases for a network product that tests basic flow control and error control.

b. A test case for database software that tests all the options of a join query.

c. A test case for a file system that checks allocation of space that is not contiguous.

d. a test case that tests the start-up of OS with normal parameters.

e. A test case corresponding to a feature that has undergone significant change in the current version.

9. Identify which category of system testing applies to each of the following case and justify your answer.

a. A customer has given his transaction load and throughput requirements. You are to recommend an appropriate hardware and software configuration for the customer.

b. Your product is web- based product with a highly seasonal usage. You want to understand the product behaviour and performance even at loads much more than the maximum expected usage so as to prepare for future expansion.

c. Your product is expected to run continuously and never stop functioning.

d. You have bought special reporting software that runs on top of an Oracle database. Recently oracle came up with a new version and the reporting software should be tested to work with this new version.

10. Identify the following as functional and non functional testing with justification.

a. Testing of documentation of the product to match the product behaviour.

b. Verification that a payroll system satisfies local tax laws.

c. Testing of the screen for user friendliness.

d. Performance qualification of a product.

e. Ensuring a certain percentage of code coverage for a product.

Course In-charge Module Coordinator HOD/IT

Dr. R. Kavitha Dr. R. Kavitha Dr. Perumalraja

UNIT – 4

1. What argument would you give to a person who says that the testing job is not challenging?

This argument is true about twenty years ago when most of the testing was manual and the products were somewhere simplistic. Normally development engineers tend to focus on specific modules. But, now testers require a holistic understanding of the entire product rather than just a single module. Suppose if the product is more complex, testing requires deep understanding of multiple domains.

In the early 1990s, most people sought to be expert in C, which moved to C++ and then to java. Similarly, interms of platforms, shifted from mainframe to client server networking to network centric computing. About ten years ago, people in the testing functions found very little parallel to these kind of “resume enriching”. In fact, now a day the use of testing tools requires programming in languages remarkably similar to those that developers use. And also the automation tests can prove to be more challenging than even developing the code for the product.

Testing is a destructive process (in the sense of finding defects in a product), there are more opportunities for out-of-box thinking.

In view of all of the above, testing offers sufficient technical challenges for an interested professional and we can say “there is testing in all development and development in all testing”.

2. What are the three types of goals in testing

✓ Business Goal

✓ Technical Goal

✓ Political Goal

3. Define the term policy

A policy can be defined as a high-level statement of principle or course of action that is used to govern a set of activities in an organization.

4. Define Test Plan

A Plan is a document that provides a frame work or approach for achieving a set of goals.

5. List the various Test Plan components

✓ Test Plan identifier

✓ Introduction

✓ Items to be tested

✓ Features to be tested

✓ Pass/Fail criteria

✓ Suspension & Resumption criteria

✓ Testing tasks

✓ Test environment

✓ Risks & Contingencies

✓ Testing costs

✓ Approvals

6. Define Features

Features may be described as distinguishing characteristics of a software component or system.

7. Define the term Pass / Fail Criteria

Given a test item and a test case, the tester must have a set of criteria to decide on whether the test has been passed or failed upon execution.

8. Define Suspension & Resumption criteria.

The criteria to suspend and resume testing are described in the simplest of cases testing is suspended at the end of a working day and resumed the following morning.

9. Define Work Breakdown Structure (WBS)

A Work Break Down structure is a hierarchical or tree like representation of all the tasks that are required to complete a project.

10. Define Risks & Contingencies.

Every testing effort has risks associated with it. Testing software with a high degree of critically, complexity, or a tight delivery deadline all imposes risks that may have negative impacts on project goals.

11. What are the various components of the test plan

✓ Test Design Specification

✓ Test Case Specification

✓ Test Procedures specifications

12. Define Test Procedure

A Procedure in general as a sequence of steps required to carry out a specific task

13. Define Test Summary Report

This report is prepared when testing is complete. It is summary of the results of the testing efforts. It also becomes a part of the projects historical database and provides a basis for lessons learned as applied to future projects.

14. List the skills needed by a Test specialist

✓ Organizational and planning skills

✓ The ability to keep track of and pay attention to details

✓ The determination to discover and solve problems

✓ The ability to mentor and train others

✓ The ability to work with users and clients

✓ The ability to think creatively

15. What are the steps in forming the test group.

✓ Upper management support for test function

✓ Establish test group organization, career paths

✓ Define education and skill levels

✓ Develop job description

✓ Interview candidates

✓ Select Test group members

16. Explain the Test team hierarchy

✓ The Test Manager

✓ The Test Lead

✓ The Test Engineer

✓ The Junior Test Engineer

✓

17. List out the skills needed for test specialist?

Test specialist must have:

• Organizational and planning skills;

• The ability to keep track of, and pay attention to, details;

• The determination to discover and solve problems;

• The ability to work with others and be able to resolve conflicts;

• The ability to mentor and train others;

• The ability to work with users and clients;

• Strong written and oral communication skills;

• The ability to work in a variety of environments;

• The ability to think creatively

18. List out the steps for formatting a testing group

[pic]

19. Summary about three critical groups in Testing Plan

Three groups were identified as critical players in the testing process

• Managers, Developers/Testers, and Users/Clients

• In TMM terminology they are called the three critical views (CV)

• Each group views the testing process from a different perspective that is related to their particular goals, needs, and requirements.

• The developers/testers work with client/user groups on quality-related activities and tasks that concern user-oriented needs.

• The focus is on soliciting client/user support, consensus, and participation in activities such as requirements analysis, usability testing, and acceptance test planning.

20. What is test incident report?

A test incident is any issue that is found during testing that requires an action(s) (e.g., defect). A Test Incident Report documents the incidents reported during testing (e.g., Unit, Integration, System, Performance, Acceptance, or Pilot). There will be one incident report for each unique incident detected.

Descriptive Question

1. Why is testing planning so important for developing a repeatable and managed testing process?

2. Why is it so important to integrate testing activities into the software life cycle?

3. What role do managers play in support of a test group?

4. Discuss in detail about the test specialist skills.

5. Discuss in detail about the test plan components.

6. Explain the concepts of test planning in detail. Also mention the way of defining test path. (AU JUNE 2018)

7. Describe the concepts of building a test group.

8. Identify the Misconception and perception about testing and discuss the issues in testing.

9. Identify the activity which is blue print for testing. What are the steps to create a test plan?

10. Construct and discuss the different organization structure of Testing team.

11. What is Test Policy? Identify the different components of test policy and discuss in detail.

12. Identify the Skills needed for Test Specialist and also discuss the steps in forming a test group.

13. Explain in detail about test report.

Course In-charge Module Coordinator HOD/IT

Dr. R. Kavitha Dr. R. Kavitha Dr. Perumalraja

UNIT – 5

1. Define the term Project monitoring.

Project Monitoring refers to the activities and tasks managers engage in to periodically check the status of each project. Reports are prepared that compare the actual work done to the work that was planned.

2. Define the term Project controlling.

Project Controlling consists of developing and applying a set of corrective actions to get a project on track when monitoring shows a deviation from what was planned.

3. Define Milestones

Milestones are tangible events that are expected to occur at a certain time in the project’s lifetime. Managers use them to determine project status.

4. List some examples of testing Milestones

✓ Completion of the Master test plan

✓ Completion of branch coverage for all units

✓ Execution of all planned system test

✓ Completion of the test summary report.

5. List various Measurements for monitoring testing status.

Coverage Measures

Test Case Development

Test Execution

Test Harness Development

6. List the types of testing measurements

✓ Coverage

✓ Test Case Development

✓ Test Execution

✓ Test Harness

7. What are the various Severity level hierarchy

✓ Catastrophic

✓ Critical

✓ Marginal

✓ Minor or Annoying

8. What are the four major activities associated with Configuration management.

✓ Identification of the Configuration items

✓ Change Control

✓ Configuration status reporting

✓ Configuration audits

9. Define Change Control Board (CCB).

There are 2 aspects of change control – one is tool based, the other term based.

The team involved is called CCB.

10. Define the term Review.

A review is a group meeting whose purpose is to evaluate a software artifact or a set of software artifact.

11. Explain the benefits of review program

✓ Higher – quality software

✓ Increased productivity

✓ Closer adherence to project schedule

✓ Increased awareness of quality issues

12. List the types of reviews.

There are two major types of technical reviews

✓ Inspections

✓ Walkthrough

12. What are the various steps in the inspection process

✓ Entry Criteria

✓ Initiation

✓ Preparation

✓ Inspection Meeting

✓ Reporting results

✓ Rework & follow up

13. Define Walkthrough

Walkthrough are a type of technical review where the producer of the reviewed material serves as the review leader and actually guides the progression of the review. Walkthrough have traditionally been applied to design and code.

15. What are the advantages of review approach. There are two pass approach for detect detection.

✓ Pass 1 has individuals first reading reviewed item

✓ Pass 2 has the item read by the group as a whole.

16. What are the various components of review plans.

✓ Review Goals

✓ Preconditions and items to be reviewed

✓ Roles, Participants, Team Size and time requirements

✓ Review Procedures

✓ Review Training

✓ Review Checklist

17. What are the various roles in review program

✓ Review Leader

✓ Review Recorder

✓ Reader

✓ Reviewer

18. List the various review team membership constituency Review Team Members

✓ SQA Staff

✓ Testers

✓ Developers

✓ Users / Clients

✓ Specialists

19. What are the various different types of software artifacts.

✓ Requirement Reviews

✓ Design Reviews

✓ Code Reviews

✓ Test Plan reviews

20. Define Defect Removal Leverage (DRL).

This is a ratio of the defect detection rates from two review or test phases and can be expressed as

Defects / hour (review or test phase X) DRL = --------------------------------------------------

Defects / hour (review or test phase Y)

Descriptive Question

1. Identify the skills needed for test automation and explain in detail.

2. Identify the generic requirements for test tool/framework and discuss in detail.

3. Explain in detail about Design and Architecture for automation testing.

4. Classify the skills for automation. Outline the scope of automation.

5. Explain in detail about Test metrics and Measurement

6. Explain in detail about project, progress and productivity metrics.

Course In-charge Module Coordinator HOD/IT

Dr. R. Kavitha Dr. R. Kavitha Dr. Perumalraja

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download