Test Strategy

What is a strategy? Why does testing need one?

A strategy outlines what to plan, and how to plan it. A successful strategy is your guide through change, and provides a firm foundation for ongoing improvement. Unlike a plan, which is obsolete from the point of creation, a strategy reflects the values of an organization - and remains current and useful.
When an organization tests its products or its tools, it tries to compare them against its expectations and values. By its nature, testing introduces change as problems are identified and resolved. A test strategy is necessary to allow these two impulses to work together. Furthermore, testing can never be said to be 'complete', and a core skill in testing is the justified management of conflicting demands; without a strategy, these judgments will be inconsistent to the point of failure.
Software development is a creative process. A test strategy is a vital enabler to this process - keeping focus on core values and consistent decision-making to help achieve desired goals with best use of resource. A good strategy stands as a clear counter to reactive, counter-productive test approaches.

Examples and Templates:

A test strategy is not a document. It is a framework for making decisions about value, and has strong links to the unique values of an organization. It is part of the creative process. Although templates exist, most organizations and projects are poorly served by a one-size-fits-all approach to their specific goals. You may find templates useful on projects where the product to be tested can be created and marketed simply by following templates - but on other projects, they're dangerous.
Workroom Productions avoids using such templates, and will create a strategy tailored to your particular needs. If you have an existing, problematic strategy, we will suggest areas where it could be slimmed down, and identify aspects that have been missed. Whether you've got documents or not, we'll help you with your strategy.
Test strategies can cover a wide range of testing and business issues. While not a checklist, you might expect to see some of the following in your own strategy:
1. values and decision-making framework
2. approaches to risk assessment, costs and quality through the organization
3. test techniques, test data, test scope and test planning
4. completion criteria and analysis
5. test management, metrics and improvement
6. skills, staffing, team structure and training
7. test environment, change control and release strategy
8. defect control, tracking and the approach to fixes
9. re-tests and regression tests
10. profiling and analysis for non-functional testing
11. test automation and test tool assessment

Testing as a genuinely strategic part of software development:

A strategic decision is one that opens up opportunities which are otherwise unapproachable - a strategic resource is the mechanism by which these opportunities are exploited.
Design, coding, and testing are the three key parts of software development. These are activities, not phases; they operate in parallel and are closely coupled. On a not-too-turbulent project, testing and defect resolution typically account for 25-35% of the final cost of development. Information produced by software testing is clearly an input to the overall organization’s strategic decisions about marketability and release - but testing can provide much more than this for the significant spends it absorbs.

Bug Report Template

A sample Bug Report Template :

Test Case Templates

It depends and vary company to company that what Test Case template it has has adopted or designed but few of them are given below :

1.















2.

Software Testing Basics

What is Software Quality Assurance?
The other technical terminology for Software Quality Assurance is Verification and Validation. To put in simple words, Verification speaks on "Are we building the right system?" and Validation speaks on "Are we building the system right?". SQA is an umbrella activity that is applied throughout the software process. Quality as the American Heritage Dictionary defines is, "A Characteristic or attribute of something..."

What is Software Testing by the way?
In general, testing is finding out how well something works. In terms of human beings, testing tells what level of knowledge or skill has been acquired. In computer hardware and software development, testing is used at key checkpoints in the overall process to determine whether objectives are being met. For example, in software development, product objectives are sometimes tested by product user representatives. When the design is complete, coding follows and the finished code is then tested at the unit or module level by each programmer; at the component level by the group of programmers involved; and at the system level when all components are combined together. At early or late stages, a product or service may also be tested for usability. At the system level, the manufacturer or independent reviewer may subject a product or service to one or more performance tests, possibly using one or more benchmarks. Whether viewed as a product or a service or both, a Web site can also be tested in various ways - by observing user experiences, by asking questions of users, by timing the flow through specific usage scenarios, and by comparing it with other sites.
The answer to the primary role of software testing is two fold:Determine whether the system meets specifications (Producer View), andDetermine whether the system meets business and user needs (Customer View)

Testing encompasses three concepts:
The demonstration of the validity of the software at each stage in the system development life cycle.Determination of the validity of the final system with respect to user needs and requirements. Examination of the behavior of a system by executing the system on sample test data.

Goal of Testing:
The primary Goal of Testing is to uncover requirement, design or coding errors in the programs. Let us look at some fundamental concepts of Software Testing. "Verification" is the process of determining whether or not the products of a given phase of software development fulfill the specifications established during the previous phase. The verification activities include proving, testing and reviews.
"Validation" is the process of evaluating the software at the end of the software development to ensure compliance with the software requirements. Testing is a common method of validation.
For high reliability we need to perform both activities. Together they are called the "V & V" activities.

Software Testing is an Art. A good tester can always be a good programmer, but a good programmer need not be a good tester.

Test Objectives:
The following can be described as test objectives as per Glen Mayer:Testing is a process of executing a program with the intent of finding an error.A good test case is one that has a high probability of finding an as-yet-undiscovered error.A successful test is one that uncovers an as-yet-undiscovered error.

Testing Principles:
The following can be described as testing principles: All tests should be traceable to customer requirements.Tests should be planned long before testing begins.The Pareto principle applies to testing. Testing should begin “in small” and progress toward testing “in large”. Exhaustive testing is not possible.To be most effective, testing should be conducted by an independent third party.

Verification Strategies:
The following can be categorized into Verification Strategies: Requirements Reviews.Design Reviews. Code Walkthrough. Code Inspection.
Validation StrategiesThe following can be described as the basic Validation Test strategies. 1. Unit Testing.2. Integration Testing.3. System Testing.4. Performance Testing.5. Alpha Testing.6. User Acceptance Testing (UAT)7. Installation Testing.8. Beta Testing.

SDLC

The stages of SDLC can be characterized and divided up in different ways, including the following:

· Project planning, feasibility study: Establishes a high-level view of the intended project and determines its goals.

· Systems analysis, requirements definition: Refines project goals into defined functions and operation of the intended application. Analyzes end-user information needs.

· Systems design: Describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudocode and other documentation.

· Implementation: The real code is written here.

· Integration and testing: Brings all the pieces together into a special testing environment, then checks for errors, bugs and interoperability.

· Acceptance, installation, deployment: The final stage of initial development, where the software is put into production and runs actual business.

· Maintenance: What happens during the rest of the software's life: changes, correction, additions, moves to a different computing platform and more. This, the least glamorous and perhaps most important step of all, goes on seemingly forever.

SDLC - VModel

A software development life cycle is the process followed when developing information systems, from the initial stage of information gathering, all the way through to maintenance and support of the system.
UKSH believes firmly in user-involvement at every stage of the process - we feel this is integral to ensuring that the system is delivered 100% to the requirements of the user, and any decisions that may be required during the system building process can be resolved efficiently.
We develop using a process known as the "V" model of systems development. At each testing stage (see diagram, below), the corresponding planning stage is referred to, ensuring the system accurately meets the goals specified in the analysis and design stages.

How to get job in Software Testing quickly?

In recent days this is the most asked question to me by readers. How to get software testing job? How to come in software testing field? or Can I get job in testing?

All these questions are similar and I want to give also similar answer for this. I have written post on choosing software testing as your career where you can analyze your abilities and know which are the most important skills required for software testing.

I will continue mentioning that “know your interest before going into any career field”. Just going to software testing career or any other hot career is wrong and which may result into loss of your job interest as well as your job.

Now you know your abilities, skills, interests right? and you have made decision to go for software testing career as it is your favorite career and you suit most in this career. So here is a guideline for how to get a good job in software testing field.

If you are a fresher and just passed out from your college or passing out in coming months then you need to prepare well for some software testing methodologies. Prepare all the manual testing concepts. If possible have some hands-on on some automation and bug tracking tools like winrunner and test director. It is always a good idea to join any software testing institute or class which will provide you a good start and direction of preparation. You can join any 4 months duration software testing course or can do diploma in software testing which is typically of 6 months to 1 year. Keep the preparation going on in your course duration. This will help you to start giving interviews right after getting over your course.

If you have some sort of previous IT experience and want to switch to software testing then it’s somewhat simple for you. Show your previous IT experience in your resume while applying for software testing jobs. If possible do some crash course to get idea of software testing concepts like I mentioned for freshers above. Keep in mind that you have some kind of IT experience so be prepared for some tough interview questions here.

As companies always prefer some kind of relevant experience for any software job, its better if you have relevant experience in software testing and QA. It may be any kind of software testing tools hands-on or some testing course from reputed institutes.

Please always keep in mind- Do not add fake experience of any kind. This can ruin your career forever. Wait and try for some more days to get the job by your abilities instead of getting into trap of fake experience.

Last important words, Software testing is not ‘anyone can do career!’ Remove this attitude from your mind if someone has told such kind of foolish thing to you. Testing requires in depth knowledge of SDLF, out of box thinking, analytical skill and some programming language skill apart from software testing basics.

So best luck and start preparation for your rocking career! I will continue writing this career series and what you actually need to prepare for software testing interview.

How to be a good tester?

It’s a every testers question. How to be a good tester?
Apart from the technical knowledge, testing skills, tester should have some personal level skills which will help them to build a good rapport in the testing team.

What are these abilities , skills which make a tester as a good tester?
Well, I was reading Dave Whalen’s article “Ugly Baby Syndrome!” and found it very interesting. Dave compared software developers with the parents who deliver a baby (software) with countless efforts. Naturally the product managers, architectures, developers spent their countless time on developing application for the customer. Then they show it to us (testers) and asks: “ How is the baby (Application)? “ And testers tell them often that they have and ugly baby. (Application with Bugs!)

Testers don’t want to tell them that they have ugly baby, but unfortunately its our job. So effectively tester can convey the message to the developers without hurting them. How can be this done? Ya that is the skill of a good tester!

Here are the tips sated by Dave to handle such a delicate situation:
Be honest and Responsive:Tell developers what are your plans to attack their application.
Be open and available:If any dev ask you to have a look at the application developed by him before the release, then politely give feedback on it and report any extra efforts needed. Don’t log the bug’s for these notes.

Let them review your tests:
If you have designed or wrote some test cases from the requirement specifications then just show them those test cases. Let them know your stuff as you are going to critic on developers work!

Use of Bug tracker:
Some testers have habit to report each and everything publicly. This attitude hurts the developers. So if you have logged any bug then let the bug tracking system report it to respective developers and managers. Also don’t each time rely on bug tracker, talk personally to developers what you logged and why you logged?

Finally some good personal points:
Don’t take it personally:Do the job of messenger. You could be a close target always. So build a thick skin!

Be prepared:
A good message in the end, Be prepared for everything! If worst things might not happened till now but they can happen at any moment in your career. So be ready to face them.

Software Testing Interview Questions

What is Acceptance Testing?
Testing conducted to enable a user/customer to determine whether to accept a software product. Normally performed to validate the software meets a set of agreed acceptance criteria.

What is Accessibility Testing?
Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).

What is Ad Hoc Testing?
A testing phase where the tester tries to 'break' the system by randomly trying the system's functionality. Can include negative testing as well. See also Monkey Testing.

What is Agile Testing?
Testing practice for projects using agile methodologies, treating development as the customer of testing and emphasizing a test-first design paradigm. See also Test Driven Development.

What is Application Binary Interface (ABI)?
A specification defining requirements for portability of applications in binary forms across defferent system platforms and environments.

What is Application Programming Interface (API)?
A formalized set of software calls and routines that can be referenced by an application program in order to access supporting system or network services.

What is Automated Software Quality (ASQ)?
The use of software tools, such as automated testing tools, to improve software quality.

What is Automated Testing?
Testing employing software tools which execute tests without manual intervention. Can be applied in GUI, performance, API, etc. testing. The use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions. What is Backus-Naur Form? A metalanguage used to formally describe the syntax of a language.

What is Basic Block?
A sequence of one or more consecutive, executable statements containing no branches.

What is Basis Path Testing?
A white box test case design technique that uses the algorithmic flow of the program to design tests.

What is Basis Set?
The set of tests derived using basis path testing.

What is Baseline?
The point at which some deliverable produced during the software engineering process is put under formal change control.

What you will do during the first day of job?

What would you like to do five years from now?
Tell me about the worst boss you've ever had.

What are your greatest weaknesses?

What are your strengths?

What is a successful product?

What do you like about Windows?

What is good code?

What are basic, core, practices for a QA specialist?

What do you like about QA?

What has not worked well in your previous QA experience and what would you change?

How you will begin to improve the QA process?

What is the difference between QA and QC?

What is UML and how to use it for testing?

What is Beta Testing?
Testing of a rerelease of a software product conducted by customers.

What is Binary Portability Testing?
Testing an executable application for portability across system platforms and environments, usually for conformation to an ABI specification.

What is Black Box Testing?
Testing based on an analysis of the specification of a piece of software without reference to its internal workings. The goal is to test how well the component conforms to the published requirements for the component.
What is Bottom Up Testing? An approach to integration testing where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.

What is Boundary Testing?
Test which focus on the boundary or limit conditions of the software being tested. (Some of these tests are stress tests).

What is Bug?
A fault in a program which causes the program to perform in an unintended or unanticipated manner.

What is Boundary Value Analysis?
BVA is similar to Equivalence Partitioning but focuses on "corner cases" or values that are usually out of range as defined by the specification. his means that if a function expects all values in range of negative 100 to positive 1000, test inputs would include negative 101 and positive 1001.

What is Branch Testing?
Testing in which all branches in the program source code are tested at least once.

What is Breadth Testing?
A test suite that exercises the full functionality of a product but does not test features in detail.

What is CAST?
Computer Aided Software Testing.

What is CMMI?

What do you like about computers?

Do you have a favourite QA book? More than one? Which ones? And why.

What is the responsibility of programmers vs QA?

What are the properties of a good requirement?

How to do test if we have minimal or no documentation about the product?

What are all the basic elements in a defect report?

Is an "A fast database retrieval rate" a testable requirement?

What is software quality assurance?

What is the value of a testing group? How do you justify your work and budget?

What is the role of the test group vis-à-vis documentation, tech support, and so forth?

How much interaction with users should testers have, and why?

How should you learn about problems discovered in the field, and what should you learn from those problems?

What are the roles of glass-box and black-box testing tools?

What issues come up in test automation, and how do you manage them?

What is Capture/Replay Tool?
A test tool that records test input as it is sent to the software under test. The input cases stored can then be used to reproduce the test at a later time. Most commonly applied to GUI test tools. 53. What is CMM? The Capability Maturity Model for Software (CMM or SW-CMM) is a model for judging the maturity of the software processes of an organization and for identifying the key practices that are required to increase the maturity of these processes.

What is CMM?
The Capability Maturity Model for Software (CMM or SW-CMM) is a model for judging the maturity of the software processes of an organization and for identifying the key practices that are required to increase the maturity of these processes.

What is Cause Effect Graph?
A graphical representation of inputs and the associated outputs effects which can be used to design test cases.

What is Code Complete?
Phase of development where functionality is implemented in entirety; bug fixes are all that are left. All functions found in the Functional Specifications have been implemented.

What is Code Coverage?
An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention.

What is Code Inspection?
A formal testing technique where the programmer reviews source code with a group who ask questions analyzing the program logic, analyzing the code with respect to a checklist of historically common programming errors, and analyzing its compliance with coding standards.

What is Code Walkthrough?
A formal testing technique where source code is traced by a group with a small set of test cases, while the state of program variables is manually monitored, to analyze the programmer's logic and assumptions.

What is Coding?
The generation of source code.

What is Compatibility Testing?
Testing whether software is compatible with other elements of a system with which it should operate, e.g. browsers, Operating Systems, or hardware.

What is Component?
A minimal software item for which a separate specification is available.

What is Concurrency Testing?
Multi-user testing geared towards determining the effects of accessing the same application code, module or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores.

What is Conformance Testing?
The process of testing that an implementation conforms to the specification on which it is based. Usually applied to testing conformance to a formal standard.

What is Context Driven Testing?
The context-driven school of software testing is flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now.

What development model should programmers and the test group use?

How do you get programmers to build testability support into their code?

What is the role of a bug tracking system?

What are the key challenges of testing?

Have you ever completely tested any part of a product? How?

Have you done exploratory or specification-driven testing?

Should every business test its software the same way?

Discuss the economics of automation and the role of metrics in testing.

Describe components of a typical test plan, such as tools for interactive products and for database products, as well as cause-and-effect graphs and data-flow diagrams.

When have you had to focus on data integrity?

What are some of the typical bugs you encountered in your last assignment?

How do you prioritize testing tasks within a project?

How do you develop a test plan and schedule?

Describe bottom-up and top-down approaches. When should you begin test planning?

When should you begin testing?

What is Conversion Testing?
Testing of programs or procedures used to convert data from existing systems for use in replacement systems.

What is Cyclomatic Complexity?
A measure of the logical complexity of an algorithm, used in white-box testing.

What is Data Dictionary?
A database that contains definitions of all data items defined during analysis.

What is Data Flow Diagram?
A modeling notation that represents a functional decomposition of a system.

What is Data Driven Testing?
Testing in which the action of a test case is parameterized by externally defined data values, maintained as a file or spreadsheet. A common technique in Automated Testing.

What is Debugging?
The process of finding and removing the causes of software failures.

What is Defect?
Nonconformance to requirements or functional / program specification

What is Dependency Testing?
Examines an application's requirements for pre-existing software, initial states and configuration in order to maintain proper functionality.

What is Depth Testing?
A test that exercises a feature of a product in full detail.

What is Dynamic Testing?
Testing software through executing it. See also Static Testing.

What is Emulator?
A device, computer program, or system that accepts the same inputs and produces the same outputs as a given system.

What is Endurance Testing?
Checks for memory leaks or other problems that may occur with prolonged execution.

What is End-to-End testing?
Testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

What is Equivalence Class?
A portion of a component's input or output domains for which the component's behaviour is assumed to be the same from the component's specification.

What is Equivalence Partitioning?
A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.

What is Exhaustive Testing?
Testing which covers all combinations of input values and preconditions for an element of the software under test.

What is Functional Decomposition?
A technique used during planning, analysis and design; creates a functional hierarchy for the software.

What is Functional Specification?
A document that describes in detail the characteristics of the product with regard to its intended features.

What is Functional Testing?
Testing the features and operational behavior of a product to ensure they correspond to its specifications. Testing that ignores the internal mechanism of a system or component and focuses solely on the outputs generated in response to selected inputs and execution conditions.

What is Glass Box Testing?
A synonym for White Box Testing.

Do you know of metrics that help you estimate the size of the testing effort?

How do you scope out the size of the testing effort?

How many hours a week should a tester work?

How should your staff be managed?

How about your overtime?

How do you estimate staff requirements?

What do you do (with the project tasks) when the schedule fails?

How do you handle conflict with programmers?

How do you know when the product is tested well enough?

What characteristics would you seek in a candidate for test-group manager?

What do you think the role of test-group manager should be? Relative to senior management? Relative to other technical groups in the company? Relative to your staff?

How do your characteristics compare to the profile of the ideal manager that you just described?

How does your preferred work style work with the ideal test-manager role that you just described?

What is different between the way you work and the role you described?

Who should you hire in a testing group and why?

What is Gorilla Testing?
Testing one particular module, functionality heavily.

What is Gray Box Testing?
A combination of Black Box and White Box testing methodologies? testing a piece of software against its specification but using some knowledge of its internal workings.

What is High Order Tests?
Black-box tests conducted once the software has been integrated.

What is Independent Test Group (ITG)?
A group of people whose primary responsibility is software testing.

What is Inspection?
A group review quality improvement process for written material. It consists of two aspects; product (document itself) improvement and process improvement (of both document production and inspection).

What is Integration Testing?
Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and functional testing. This type of testing is especially relevant to client/server and distributed systems.

What is Installation Testing?
Confirms that the application under test recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions.

What is Localization Testing?
This term refers to making software specifically designed for a specific locality.

What is Loop Testing?
A white box testing technique that exercises program loops.

What is Metric?
A standard of measurement. Software metrics are the statistics describing the structure or content of a program. A metric should be a real objective measurement of something such as number of bugs per lines of code.

What is Monkey Testing?
Testing a system or an Application on the fly, i.e just few tests here and there to ensure the system or an application does not crash out.

What is Negative Testing?
Testing aimed at showing software does not work. Also known as "test to fail". See also Positive Testing.

What is Path Testing?
Testing in which all paths in the program source code are tested at least once.

What is Performance Testing?
Testing conducted to evaluate the compliance of a system or component with specified performance requirements. Often this is performed using an automated test tool to simulate large number of users. Also know as "Load Testing".

What is Positive Testing?
Testing aimed at showing software works. Also known as "test to pass". See also Negative Testing.

What is Quality Assurance?
All those planned or systematic actions necessary to provide adequate confidence that a product or service is of the type and quality needed and expected by the customer.

What is Quality Audit?
A systematic and independent examination to determine whether quality activities and related results comply with planned arrangements and whether these arrangements are implemented effectively and are suitable to achieve objectives.

What is Quality Circle?
A group of individuals with related interests that meet at regular intervals to consider problems or other matters related to the quality of outputs of a process and to the correction of problems or to the improvement of quality.

What is Quality Control?
The operational techniques and the activities used to fulfill and verify requirements of quality.

What is Quality Management?
That aspect of the overall management function that determines and implements the quality policy.

What is Quality Policy?
The overall intentions and direction of an organization as regards quality as formally expressed by top management.

What is Quality System?
The organizational structure, responsibilities, procedures, processes, and resources for implementing quality management.

What is Race Condition?
A cause of concurrency problems. Multiple accesses to a shared resource, at least one of which is a write, with no mechanism used by either to moderate simultaneous access.

What is Ramp Testing?
Continuously raising an input signal until the system breaks down.

What is Recovery Testing?
Confirms that the program recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions.

What is Release Candidate?
A pre-release version, which contains the desired functionality of the final version, but which needs to be tested for bugs (which ideally should be removed before the final version is released).

What is Sanity Testing?
Brief test of major functional elements of a piece of software to determine if its basically operational. See also Smoke Testing.

What is Scalability Testing?
Performance testing focused on ensuring the application under test gracefully handles increases in work load.

What is the role of metrics in comparing staff performance in human resources management?

How do you estimate staff requirements?

What do you do (with the project staff) when the schedule fails?

Describe some staff conflicts youÂ’ve handled.

Why did you ever become involved in QA/testing?

What is the difference between testing and Quality Assurance?

What was a problem you had in your previous assignment (testing if possible)?How did you resolve it?

What are two of your strengths that you will bring to our QA/testing team?

What do you like most about Quality Assurance/Testing?

What do you like least about Quality Assurance/Testing?

What is the Waterfall Development Method and do you agree with all the steps?

What is the V-Model Development Method and do you agree with this model?

What is Security Testing?
Testing which confirms that the program can restrict access to authorized personnel and that the authorized personnel can access the functions available to their security level.

What is Smoke Testing?
A quick-and-dirty test that the major functions of a piece of software work. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire.

What is Soak Testing?
Running a system at high load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of transactions have been executed.

What is Software Requirements Specification?
A deliverable that describes all data, functional and behavioral requirements, all constraints, and all validation requirements for software.

What is Software Testing?
A set of activities conducted with the intent of finding errors in software.

What is Static Analysis?
Analysis of a program carried out without executing the program.

What is Storage Testing?
Testing that verifies the program under test stores data files in the correct directories and that it reserves sufficient space to prevent unexpected termination resulting from lack of space. This is external storage as opposed to internal storage.

What is Stress Testing?
Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the load under which it fails and how. Often this is performance testing using a very high level of simulated load.

What is Structural Testing?
Testing based on an analysis of internal workings and structure of a piece of software. See also White Box Testing.

What is System Testing?
Testing that attempts to discover defects that are properties of the entire system rather than of its individual components.

What is Testability?
The degree to which a system or component facilitates the establishment of test criteria and the performance of tests to determine whether those criteria have been met.

What is Test Bed?
An execution environment configured for testing. May consist of specific hardware, OS, network topology, configuration of the product under test, other application or system software, etc. The Test Plan for a project should enumerated the test beds(s) to be used.

What is Test Case?
Test Case is a commonly used term for a specific test. This is usually the smallest unit of testing. A Test Case will consist of information such as requirements testing, test steps, verification steps, prerequisites, outputs, test environment, etc. A set of inputs, execution preconditions, and expected outcomes developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.

Test Driven Development?
Testing methodology associated with Agile Programming in which every chunk of code is covered by unit tests, which must all pass all the time, in an effort to eliminate unit-level and regression bugs during development. Practitioners of TDD write a lot of tests, i.e. an equal number of lines of test code to the size of the production code.

What is Test Environment?
The hardware and software environment in which tests will be run, and any other software with which the software under test interacts when under test including stubs and test drivers.

What is Test First Design?
Test-first design is one of the mandatory practices of Extreme Programming (XP).It requires that programmers do not write any production code until they have first written a unit test.

What is Test Plan?
A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning. Ref IEEE Std 829.

What is Test Specification?
A document specifying the test approach for a software feature or combination or features and the inputs, predicted results and execution conditions for the associated tests.

What is Test Suite?
A collection of tests used to validate the behavior of a product. The scope of a Test Suite varies from organization to organization. There may be several Test Suites for a particular product for example. In most cases however a Test Suite is a high level concept, grouping together hundreds or thousands of tests related by what they are intended to test.

What is Thread Testing?
A variation of top-down testing where the progressive integration of components follows the implementation of subsets of the requirements, as opposed to the integration of components by successively lower levels.

What is Top Down Testing?
An approach to integration testing where the component at the top of the component hierarchy is tested first, with lower level components being simulated by stubs. Tested components are then used to test lower level components. The process is repeated until the lowest level components have been tested.

What is Total Quality Management?
A company commitment to develop a process that achieves high quality product and customer satisfaction.

What is Traceability Matrix?
A document showing the relationship between Test Requirements and Test Cases.

What is Use Case?
The specification of tests that are conducted from the end-user perspective. Use cases tend to focus on operating software as an end-user would conduct their day-to-day activities.

What is Validation?
The process of evaluating software at the end of the software development process to ensure compliance with software requirements. The techniques for validation is testing, inspection and reviewing.

What is Verification?
The process of determining whether of not the products of a given phase of the software development cycle meet the implementation steps and can be traced to the incoming objectives established during the previous phase. The techniques for verification are testing, inspection and reviewing.

Describe some problem that you had with automating testing tool. How do you plan test automation?

Can test automation improve test effectiveness?

What is data - driven automation?

What are the main attributes of test automation?

Does automation replace manual testing?

How will you choose a tool for test automation? How you will evaluate the tool for test automation?

What are main benefits of test automation?

What could go wrong with test automation?

How you will describe testing activities?

What testing activities you may want to automate?

User Acceptance Testing

For years, User Acceptance Test (UAT) has been synonymous with screen testing. This is logical because for years most of the user experience was what was on the screen. With today’s integrated systems, validating the user experience means going behind the screens to ensure the user’s data has been recorded into downstream applications correctly.
Therefore, UAT needs to be defined as more than simply screens. UAT teams need easy, automated ways of accessing the behind the screens information flow for validation. By using Solstice’s recording capability to create back-end tests, UAT teams can develop detailed tests to expose critical data that is important to users but is displayed on screens. Further, once errors are found, the detailed back-end test can pinpoint exactly where and what has caused a problem. Solstice gives UAT teams the increased visibility demanded by today’s integrated systems.