Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
com
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
3. Design the system – The System Architecture Team designs the system and write
Functional Design Document. During design phase general solutions re hypothesized
and data and process structures are organized.
4. Build the system – The System Specifications and design documents are given to the
development team code the modules by following the Requirements and Design
document.
5. Test the system - The test team develops the test plan following the requirements. The
software is build and installed on the test platform after developers have completed
development and Unit Testing. The testers test the software by following the test plan.
6. Deploy the system – After the user-acceptance testing and certification of the software,
it is installed on the production platform. Demos and training are given to the users.
7. Support the system - After the software is in production, the maintenance phase of the
life begins. During this phase the development team works with the development
document staff to modify and enhance the application and the test team works with the
test documentation staff to verify and validate the changes and enhancement to the
application software.
Explain the pre testing phase, acceptance testing and testing phase.
Pre testing Phase:
1. Review the requirements document for the testability: Tester will use the
requirement document to write the test cases.
2. Establishing the hard freeze date: Hard freeze date is a date after which system test
team will not accept any more software and documentation changes from development
team, unless they are fixes of severity 1 MR’s. The date is scheduled so that product test
team will have time for final regression.
3. Writing master test plan: It is written by the lead tester or test coordinator. Master
test plan includes entire testing plan, testing resources and testing strategy.
4. Setting up MR Tool: The MR tool must be set as soon as you know of the different
modules in the product, the developers and testers on the product, the hardware
platform, and operating system testing will be done.
This information will be available upon the completion of the first draft of the
architecture document. Both testers and developers are trained how to use the system.
5. Setting up the test environment: The test environment is set on separate machines,
database and network. This task is performed by the technical support team. First time
it takes some time, Afterwards the same environment can be used by the later releases.
6. Writing the test plan and test cases: Template and the tool is decided to write the
test plan, test cases and test procedures. Expected results are organized in the test plan
according to the feature categories specified in the requirement document. For each
feature positive and negative test cases are written. Writing test plan requires the
complete understanding of the product and its interfaces with other systems. After test
For more questions-checkout: www.futurethoughtsllc.com
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
plan is completed, a walkthrough is conducted with the developers and design team
members to baseline the test plan document.
7. Setting up the test automation tool: Planning of test strategy on how to automate the
testing. Which test cases will be executed for regression testing. Not all the test cases
will be executed during regression testing.
8. Identify acceptance test cases: Select subsets that are expected on the first day of
system test. These tests must pass to accept the product in the system test.
What is the value of a testing group? How do you justify your work and budget?
All software products contain defects/bugs, despite the best efforts of their development
teams. It is important for an outside party (one who is not developer) to test the product
from a viewpoint that is more objective and representative of the product user.
Testing group test the software from the requirements point of view or what is required by
the user. Testers job is to examine a program and see if it does not do what it is
supposed to do and also see what it does what it is not supposed to do.
What is master test plan? What it contains? Who is responsible for writing it?
OR
What is a test plan? Who is responsible for writing it? What it contains.
OR
What's a 'test plan'? What did you include in a test plan?
A software project test plan is a document that describes the objectives, scope, approach,
and focus of a software testing effort. The process of preparing a test plan is a useful way to
think through the efforts needed to validate the acceptability of a software product. The
completed document will help people outside the test group understand the 'why' and 'how'
of product validation. It should be thorough enough to be useful but not so thorough that no
For more questions-checkout: www.futurethoughtsllc.com
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
one outside the test group will read it. The following are some of the items that might be
included in a test plan, depending on the particular project:
• Title
• Identification of software including version/release numbers
• Revision history of document including authors, dates, approvals
• Table of Contents
• Purpose of document, intended audience
• Objective of testing effort
• Software product overview
• Relevant related document list, such as requirements, design documents, other test
plans, etc.
• Relevant standards or legal requirements
• Trace ability requirements
• Relevant naming conventions and identifier conventions
• Overall software project organization and personnel/contact-info/responsibilties
• Test organization and personnel/contact-info/responsibilities
• Assumptions and dependencies
• Project risk analysis
• Testing priorities and focus
• Scope and limitations of testing
• Test outline - a decomposition of the test approach by test type, feature,
functionality, process, system, module, etc. as applicable
• Outline of data input equivalence classes, boundary value analysis, error classes
• Test environment - hardware, operating systems, other required software, data
configurations, interfaces to other systems
• Test environment validity analysis - differences between the test and production
systems and their impact on test validity.
• Test environment setup and configuration issues
• Software migration processes
• Software CM processes
• Test data setup requirements
• Database setup requirements
• Outline of system-logging/error-logging/other capabilities, and tools such as screen
capture software, that will be used to help describe and report bugs
• Discussion of any specialized software or hardware tools that will be used by testers
to help track the cause or source of bugs
• Test automation - justification and overview
• Test tools to be used, including versions, patches, etc.
• Test script/test code maintenance processes and version control
• Problem tracking and resolution - tools and processes
• Project test metrics to be used
• Reporting requirements and testing deliverables
For more questions-checkout: www.futurethoughtsllc.com
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
What are the entrance and exit criteria in the system test?
Entrance and exit criteria of each testing phase is written in the master test plan.
Enterence Criteria:
- Integration exit criteria have been successfully met.
- All installation documents are completed.
- All shippable software has been successfully built
- Syate, test plan is baselined by completing the walkthrough of the test plan.
- Test environment should be setup.
- All severity 1 MR’s of integration test phase should be closed.
Exit Criteria:
- All the test cases in the test plan should be executed.
- All MR’s/defects are either closed or deferred.
- Regression testing cycle should be executed after closing the MR’s.
- All documents are reviewed, finilized and signed-off.
If there are no requirements, how will you write your test plan?
If there are no requirements we try to gather as much details as possible from:
• Business Analysts
• Developers (If accessible)
• Previous Version documentation (if any)
• Stake holders (If accessible)
For more questions-checkout: www.futurethoughtsllc.com
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
• Prototypes.
What knowledge you require to do white box, integration and black box testing?
For white box testing you need to understand the internals of the module like data
structures and algorithms and have access to the source code and for black box testing only
understanding/functionality of the application.
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
In any application new functionalities can be added so the application has to be tested to see
whether the added functionalities have affected the existing functionalities or not. Here
instead of retesting all the existing functionalities baseline scripts created for these can be
rerun and tested.
What is the difference between regression automation tool and performance automation
tool?
Regression testing tools capture test and play them back at a later time. The capture and
playback feature is fundamental to regression testing.
Performance testing tool determine the load a server can handle. And must have feature to
stimulate many users from one machine, scheduling and synchronize different users, able to
measure the network load under different number of simulated users.
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
What is stress testing, performance testing, Security testing, Recovery testing and volume
testing.
Stress testing: Testing the system if it can handle peak usage period loads that result from
large number of simultaneous users, transactions or devices. Monitoring should be
performed for throughput and system stability.
Performance Testing: Testing the system whether the system functions are being performed
in an acceptable timeframe under simultaneous user load. Timings for both read and
update transactions should be gathered to determine whether. This should be done stand-
alone and then in a multi-user environment to determine the transaction throughput.
Security Testing: Testing the system for its security from unauthorized use and
unauthorized data access.
Recovery Testing: Testing a system to see how it responds to errors and abnormal
conditions, such as system crash, loss of device, communications, or power.
Volume Testing: Testing to the system to determine if it can correctly process large volumes
of data fed to the system. Systems can often respond unpredictably when large volume
causes files to overflow and need extensions.
What is MR?
MR is a Modification Request also known as Defect Report, a request to modify the
program so that program does what it is supposed to do.
For more questions-checkout: www.futurethoughtsllc.com
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
What criteria you will follow to assign severity and due date to the MR?
Defects (MR) are assigned severity as follows:
Critical: show stoppers (the system is unusable)
High: The system is very hard to use and some cases are prone to convert to critical issues if
not taken care of.
Medium: The system functionality has a major bug but is not too critical but needs to be
fixed in order for the AUT to go to production environment.
Low: cosmetic (GUI related)
If the functionality of an application had an inbuilt bug because of which the test script
fails, would you automate the test?
No, we do the automation once the application is tested manually and it is stabilized.
Automation is for regression testing.
You find a bug and the developer says “It’s not possible” what do u do?
I’ll discuss with him under what conditions (working environment) the bug was produced.
I’ll provide him with more details and the snapshot of the bug.
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
V – Model
Agile
[Or talk about Customized methodology of the specific client]
The Capability Maturity Model Integration (CMMI) provides the guidance for improving
your organization's processes and your ability to manage the development, acquisition, and
maintenance of products and services. CMM Integration places proven practices into a
structure that helps your organization assess its organizational maturity and process area
capability, establish priorities for improvement, and guide the implementation of these
improvements.
The new integrated model (CMMI) uses Process Areas (known as PAs) which are different
to the previous model, and covers as well systems as software processes, rather than only
software processes as in the SW-CMM.
What is ODBC?
Open Database Connectivity (ODBC) is an open standard application-programming
interface (API) for accessing a database. ODBC is based on Structured Query Language
(SQL) Call-Level Interface. It allows programs to use SQL requests that will access
databases without having to know the proprietary interfaces to the databases. ODBC
handles the SQL request and converts it into a request the individual database system
understands.
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
A tool has been developed that uses UML state charts produced by Rational Software
Corporation's Rational Rose tool to generate test data.
Describe some problems that you had with automation testing tools
One of the problems with Automation tools is Object recognition
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
Have you ever written test cases or did you just execute those written by others?
Yes, I was involved in preparing and executing test cases in all the project.
Realising you won’t be able to test everything-how do you decide what to test first? OR
What if there isn't enough time for thorough testing?
Use risk analysis to determine where testing should be focused. Since it's rarely possible to
test every possible aspect of an application, every possible combination of events, every
For more questions-checkout: www.futurethoughtsllc.com
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
If automating-what is your process for determining what to automate and in what order?
OR
Can you automate all the test scripts? Explain ? OR
How do you plan test automation? OR
What criteria do you use when determining when to automate a test or leave it manual?
1. Test that need to be run for every build of the application
2. Tests that use multiple data values for the same actions( data driven tests)
3. Tests that require detailed information from application internals
4. Stress/ load testing
If you’re given a program that will average student grades, what kinds of inputs would you
use?
Name of student, Subject, Score
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
5. Identify mismatches, report defect to the development team using defect reporting tool.
6. Track defect, perform regression test to verify that defect is fixed and did not disturb
other parts of the application.
7. Once all the defects are closed and application is stabilized, automate the test scripts for
regression and performance testing.
What are Individual test case and Workflow test case? Why we do workflow scenarios
An individual test is one that is for a single features or requirement. However, it is
important that related sequences of features be tested as well, as these correspond to units
of work that user will typically perform. It will be important for the system tester to become
familiar with what users intend to do with the product and how they intend to do it. Such
testing can reveal errors that might not ordinarily be caught otherwise. For example while
each operations in a series might produce the correct results it is possible that intermediate
results get lost or corrupted between operations.
Validation: typically involves actual testing and takes place after verifications are
completed. The term 'IV & V' refers to Independent Verification and Validation
For more questions-checkout: www.futurethoughtsllc.com
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
What do you mean by “set up the test environment and provide full platform support?
We need to provide the following for setting up the environment
1) Required software
2) Required hardware
3) Required testing tools
4) Required test data
After providing these we need to provide support for any problems that occur during the
testing process.
If you have shortage of time, how would you prioritize you testing?
Use risk analysis to determine where testing should be focused. Since it's rarely possible to
test every possible aspect of an application, every possible combination of events, every
dependency, or everything that could go wrong, risk analysis is appropriate to most
software development projects. Considerations can include:
• Which functionality is most important to the project's intended purpose?
• Which functionality is most visible to the user?
• Which functionality has the largest safety impact?
• Which functionality has the largest financial impact on users?
• Which aspects of the application are most important to the customer?
• Which aspects of the application can be tested early in the development cycle?
For more questions-checkout: www.futurethoughtsllc.com
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
• Which parts of the code are most complex, and thus most subject to errors?
• Which parts of the application were developed in rush or panic mode?
• Which aspects of similar/related previous projects caused problems?
• Which aspects of similar/related previous projects had large maintenance expenses?
• Which parts of the requirements and design are unclear or poorly thought out?
• What do the developers think are the highest-risk aspects of the application?
• What kinds of problems would cause the worst publicity?
• What kinds of problems would cause the most customer service complaints?
• What kinds of tests could easily cover multiple functionalities?
• Which tests will have the best high-risk-coverage to time-required ratio?
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
How do you analyze your test results? what metrics do you try to provide?
OR
How do you view test results?
Test log is created for analyzing the test results.This is a chronological record of the Test
executions and events that happened during testing. It includes the following sections:
Description: What’s being tested, including Version ID, where testing is being done, what
hardware and all other configuration information.
Activity and Event Entries: What happened including Execution Description: The
procedure used.
Procedure Result: What happened. What did you see and where did you store the output?
Environment Information: Any changes (hardware substitution) made specifically for this
test.
Unexpected Events: What happened before and after problem/bug occurred.
Incident/Bug Report Identifiers: Problem Report number
If you come onboard, give me a general idea of what your first overall tasks will be as far as
as starting a quality effort?
Try to learn about the application, Environment and Prototypes to have the better
understanding of application and existing testing efforts
How do you differentiate the roles of Quality Assurance Manager and Project Manager?
Quality assurance manager responsibilites includes seting up the standards, the
methodology and the strategies for testing the application and providing guidelines to the
QA team. Project Manager is reponsible to testing and development activities.
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
A three-tier system is one that has presentation components, business logic and data access
physically running on different platforms. Web applications are perfect for three-tier
architecture, as the presentation layer is necessarily separate, and the business and data
components can be divided up much like a client-server application
What is Internet?
The Internet, sometimes called simply "the Net," is a worldwide system of computer
networks - a network of networks in which users at any one computer can, if they have
permission, get information from any other computer. Physically, the Internet uses a
portion of the total resources of the currently existing public telecommunication networks.
Technically, what distinguishes the Internet is its use of a set of protocols called TCP/IP (for
Transmission Control Protocol/Internet Protocol). Two recent adaptations of Internet
technology, the intranet and the extranet, also make use of the TCP/IP protocol.
What is Intranet?
An intranet is a private network that is contained within an enterprise. It may consist of
many interlinked local area networks and also use leased lines in the Wide Area Network.
The main purpose of an intranet is to share company information and computing resources
among employees. An intranet can also be used to facilitate working in groups and for
teleconferences.
What is Extranet?
An extranet is a private network that uses the Internet protocol and the public
telecommunication system to securely share part of a business's information or operations
with suppliers, vendors, partners, customers, or other businesses. An extranet can be
viewed as part of a company's intranet that is extended to users outside the company. It has
also been described as a "state of mind" in which the Internet is perceived as a way to do
business with other companies as well as to sell products to customers.
What is ISO-9000?
For more questions-checkout: www.futurethoughtsllc.com
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
A set of international standards for both quality management and quality assurance that
has been adopted by over 90 countries worldwide. The ISO 9000 standards apply to all
types of organizations, large and small, and in many industries. The ISO 9000 series
classifies products into generic product categories: hardware, software, processed
materials, and services.
What is QMO?
The QMO is a set of processes and guidelines that software systems projects and products
that are built under a contract (with a customer ) must follow to comply with ISO-9000
standards. ISO-9000 states that the guidelines for software development must be
documented.
What is an Object?
An object is a software bundle of related variables and methods. Software objects are often
used to model real-world objects you find in everyday life
What is class?
A class is a blueprint or prototype that defines the variables and the methods common to all
objects of a certain kind.
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
What development model should programmers and the test group use?
A Development Model, which helps adopt a structured approach in assessment, design,
integration and implementation of a project and in extending relevant training and support.
Each of these stages is necessarily accompanied with client inputs, checkpoints and reviews
to ensure successful systems implementation.
Basically there are many types of development models to support the development of high-
quality software products. The two most widely used models are Waterfall and Spiral
development model.
Waterfall development model encourages the development team to specify the business
functionality of the software prior to developing a system.
Spiral development model combines the waterfall development model and the prototype
approach, which is a series of partial implementations of the product.
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
How do you promote the concept of phase containment and defect prevention?
Phase Containment refers to detecting and correcting defects in the same phase in which
they’re created.
The purpose of Defect Prevention is to identify the cause of defects and prevent them from
recurring.
What is Walkthrough?
Walkthrough : A 'walkthrough' is an informal meeting for evaluation or informational
purposes. Little or no preparation is usually required.
OR
A process in which a developer leads one or more members of the development team
through a segment of an artifact that he or she has written while the other members ask
questions and make comments about technique, style, possible error, violation of
development standards, and other problems.
What is inspection?
Inspection: An inspection is more formalized than a 'walkthrough', typically with 3-8
people including a moderator, reader, and a recorder to take notes. The subject of the
inspection is typically a document such as a requirements spec or a test plan, and the
purpose is to find problems and see what's missing, not to fix anything. Attendees should
prepare for this type of meeting by reading thru the document; most problems will be found
during this preparation. The result of the inspection meeting should be a written report.
Thorough preparation for inspections is difficult, painstaking work, but is one of the most
cost effective methods of ensuring quality.
OR
For more questions-checkout: www.futurethoughtsllc.com
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
1. What is verification?
A: Verification ensures the product is designed to deliver all functionality to the customer; it
typically involves reviews and meetings to evaluate documents, plans, code, requirements and
specifications; this can be done with checklists, issues lists, and walkthroughs and inspection
meetings.
2. What is validation?
For more questions-checkout: www.futurethoughtsllc.com
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
3. What is a walkthrough?
A: A walkthrough is an informal meeting for evaluation or informational purposes. A
walkthrough is also a process at an abstract level. It's the process of inspecting software code by
following paths through the code (as determined by input conditions and choices made along the
way). The purpose of code walkthroughs is to ensure the code fits the purpose. Walkthroughs also
offer opportunities to assess an individual's or team's competency.
4. What is quality?
A: Quality software is software that is reasonably bug-free, delivered on time and within budget,
meets requirements and expectations and is maintainable
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
properties. Requirements should be clear, complete, reasonably detailed, cohesive, attainable and
testable.
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
case templates contain all particulars of every test case. Often these templates are in the form of a
table. One example of this table is a 6-column table, where column 1 is the "Test Case ID
Number", column 2 is the "Test Case Name", column 3 is the "Test Objective", column 4 is the
"Test Conditions/Setup", column 5 is the "Input Data Requirements/Steps", and column 6 is the
"Expected Results". All documents should be written to a certain standard and template.
Standards and templates maintain document uniformity. They also help in learning where
information is located, making it easier for users to find what they want
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
A. Performance testing verifies loads, volumes and response times, as defined by requirements.
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
Testers should understand these gaps and use them after getting this signed off from the author of
the FS .The final FS form may vary from the original
44. What if the application has functionality that wasn't in the requirements?
A: It may take serious effort to determine if an application has significant unexpected or hidden
functionality, which it would indicate deeper problems in the software development process. If
the functionality isn't necessary to the purpose of the application, it should be removed, as it may
have unknown impacts or dependencies that were not taken into account by the designer or the
customer.
45. Why do you recommend that we test during the design phase?
A: Because testing during the design phase can prevent defects later on. We recommend verifying
three things...
1. Verify the design is good, efficient, compact, testable and maintainable.
2. Verify the design meets the requirements and is complete (specifies all relationships between
modules, how to pass data, what happens in exceptional circumstances, starting state of each
module and how to guarantee the state of each module).
3. Verify the design incorporates enough memory, I/O devices and quick enough runtime for the
final product.
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
A: Generally speaking, there are bugs in software because of unclear requirements, software
complexity, programming errors, changes in requirements, errors made in bug tracking, time
pressure, poorly documented code and/or bugs in tools used in software development.
48. Give me five common problems that occur during software development.
A: Poorly written requirements, unrealistic schedules, inadequate testing, adding new features
after development is underway and poor communication.
1. Requirements are poorly written when requirements are unclear, incomplete, too general, or
not testable; therefore there will be problems.
2. The schedule is unrealistic if too much work is crammed in too little time.
3. Software testing is inadequate if none knows whether or not the software is any good until
customers complain or the system crashes.
4. It's extremely common that new features are added after development is underway.
5. Miscommunication either means the developers don't know what is needed, or customers have
unrealistic expectations and therefore problems are guaranteed.
52. What if the project isn't big enough to justify extensive testing?
A: Consider the impact of project errors, not the size of the project. However, if extensive testing
is still not justified, risk analysis is again needed and the considerations listed under "What if
For more questions-checkout: www.futurethoughtsllc.com
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
there isn't enough time for thorough testing?" do apply. The test engineer then should do "ad hoc"
testing, or write up a limited test plan based on the risk analysis.
Mail - 1
Who writes business requirements? What you do when you have BRD?
Business Analyst writes the Business Requirements. Business requirements (BR) are sent to
the software architect (SA) for validation. SA after understanding the BR makes use cases and
UML diagrams and forwards them to QA manager. QA manager based on scope, BR, use case &
UML diagram writes the overall testing strategy & high-level test cases and forward them to
testers.
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
Mail - 2
1) Please see the Attached sample test plan template
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
13. Deploy the system – After the user-acceptance testing and certification of the
software, it is installed on the production platform. Demos and training are given to
the users.
14. Support the system - After the software is in production, the maintenance phase of the
life begins. During this phase the development team works with the development
document staff to modify and enhance the application and the test team works with
the test documentation staff to verify and validate the changes and enhancement to
the application software.
QA process starts from the second phase of the Software Development Life Cycle i.e.
Define the System. Actual Product testing will be done on Test the system phase (Phase-
5). During this phase test team will verify the actual results against expected results.
Test plan
A software project test plan is a document that describes the objectives, scope, approach,
and focus of a software testing effort.
• Outside test organizations to be utilized and their purpose, responsibilities,
deliverables, contact persons, and coordination issues
Need the Business requirement document to prepare the test plan. Test plan controls the
entire testing process. Testers have to follow this test plan during the entire testing
process. Entrance and exit criteria of each testing phase is written in the master test plan.
Enterence Criteria:
- Integration exit criteria have been successfully met.
- All installation documents are completed.
- All shippable software has been successfully built
- System, test plan is base lined by completing the walkthrough of the test
plan.
- Test environment should be setup.
- All severity 1 MR’s of integration test phase should be closed.
Exit Criteria:
- All the test cases in the test plan should be executed.
- All MR’s/defects are either closed or deferred.
- Regression testing cycle should be executed after closing the MR’s.
- All documents are reviewed, finilized and signed-off.
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
application has a well-designed architecture with tight code; may require developing test
driver modules or test harnesses.
Mail -3
Testing Types:
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
To make sure that the test coverage as extensive we can prepare a traceability matrix. This could
be a simple excel having one column as the functional specification, the next column could be the
test case name and finally the last column could be the test script id.
After preparation of this document we can uniquely identify each requirement is matched to a test
case and a test script.
This is the best way to track the test coverage. Though a tedious process but this process has
certainly proved to be effective if followed properly.
7. What is QA methodology and what environment would you use to do your QA testing?
QA Testing Methodology: Plan Phase, Capture Phase, Record Phase, Run Phase, Track Phase.
For testing the environment is different from development environment and H/w and S/W
requirements depend on the application.
11. What is the compatibility testing difference between testing IE explorer and testing in firefox?
Compatibility Testing: The testing processes with ability of testing two or more systems
exchange the information in the case if this newly developed s/w. The access should be carried
out comparability problems between new s/w and other programs.
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
17. In a situation where actual result doesn’t match with expected result, what would you do?
You have to register it as a bug and you have to decide the priority, severity and register it in bug
tracking tool so your test lead, developer and project manager get noticed that.
20. What is the difference between test scenario and test case?
Test Scenario: From Use Case & Functionality Requirement of the Application Test Case: From
Test Scenario (Use Case & Functionality Requirement) of App.
21. What is the difference between smoke testing and sanity testing?
In Smoke testing we test the main functionality of the system instead of testing the whole system
In Sanity testing we test that system is stable till the end of the testing and not get crashed.
22. What are all the scenarios to be considered while testing reports?
The purpose of the Report generation is to produce lot of data about the system based on
selected criteria. A particular report displays the data from the different modules which are linked
in one or other way. So while testing the Report we should first understand the relation between
different modules about how they are linked each other and how the data flows from the one
module from other. There may be different stages in which data flows. Generate the Report in
each stage and make a check data is being displayed properly or not in the Report. If the data
flows through the different work flows (which is case in most of the Reports), generate the Report
at the every activity through out the work flow. Create some 4 to 5 work flow instances and keep
all these instances at different stages and generate Report and make check whether data is
displayed properly or not. Also make sure that data is being displayed under the proper fields in
the generated report.
23. How do you know all the testing scenarios are covered?
For more questions-checkout: www.futurethoughtsllc.com
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
24. If test cases are executed with existing requirements and the requirements are frequently
changing, what steps should be taken for the test completion?
You have to edit/update the test cases on a regular basis. As the part of Requirements
Management, any changes in the requirements will be added/edited to the SRS.
29. What is the difference between boundary value analysis and equivalence portioning?
Boundary value Analysis: is based on testing on and around the boundaries between partitions.
i.e. Extreme values of the range. Equivalence partitioning: Divide or partition a set of test
conditions into groups or sets that can be considered same or equal, hence equivalence
partitioning. Also called as equivalence classes.
31. What is the diff between quality control and quality assurance?
Quality assurance is set of activities designed to ensure that maintenance process is adequate
to ensure a system will meet it object. Quality control is set of activities designed to evaluate a
developed work product
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
Organizations vary considerably in how they assign responsibility for QA and testing,
sometimes they’re the combined responsibility of one group or individual. Also common
are project teams that include a mix of testers and developers who work closely together,
with overall QA processes monitored by project managers. It will depend on what best
fits an organization’s size and business structure.
1. What types of documents would you need for QA, QC, and Testing?
BRD, FRD
7. What is the difference between QA and testing? Read the answer for this interview
question for software testers
QA is assuring the application is bug free
Testing is executing the applications, documenting all the results & defects.
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
13. Describe to me what you see as a process. Not a particular process, just the basics of having a
process.
14. Describe to me when you would consider employing a failure mode and effect analysis.
15. Describe to me the Software Development Life Cycle as you would define it.
Initiate, Define, Design, Build, Test, Deploy & Support
17. How do you differentiate the roles of Quality Assurance Manager and Project Manager?
QA Manager is the one who will manage all the QA Testers. Project Manager will be managing
all the developers and the whole project.
18. Tell me about any quality efforts you have overseen or implemented. Describe some of the
challenges you faced and how you overcame them.
19. How do you deal with environments that are hostile to quality change efforts?
20. In general, how do you see automation fitting into the overall process of testing?
If the application is too big it should be tested by automation. Also if the application is going to
be in regression testing it should be automated
21. How do you promote the concept of phase containment and defect prevention?
22. If you come onboard, give me a general idea of what your first overall tasks will be as far as
starting a quality effort.
For more questions-checkout: www.futurethoughtsllc.com
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
Understanding the project thoroughly by reading the BRD, Creating test plans & documents for
that project & attending the meetings to improve my knowledge of this new project
25. Have you ever written test cases or did you just execute those written by others?
Most of the times I have written the test cases and executed them, but there were times when I
had to execute the existing test case due to addition of new modules
29. How do you test if you have minimal or no documentation about the product?
To run the test we have to have the proper documents but if there are no documents about the
product we should have meetings with the developers and the users, discuss the product.
Character Traits
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
A. Security is the basic need. The only true job security comes from making a meaningful
contribution to my employer. I am confident that I will be able to continue getting the
work done always exceeding expectations.
3.Do you get bored doing the same work over and over again?
A. Not really, if the work involves my job. I don’t get bored because it is my
responsibility to complete it.
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
16.Do you speak up if your point of view differs from that of your superiors?
A. I am careful about expressing my opinions.
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
A. Self-Starter
B. Highly motivated
C. Energetic
D. Results oriented
E. Enthusiasm and energy are contagious. I am infected with both.
F. As a result the groups I’ve worked become very successful.
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
What is the V-Model Development Method and do you agree with this model?
What is the Capability Maturity Model (CMM)? At what CMM level were the last
few companies you worked?
What is a "Good Tester"?
Could you tell me two things you did in your previous assignment (QA/Testing
related hopefully) that you are proud of?
List 5 words that best describe your strengths.
What are two of your weaknesses?
What methodologies have you used to develop test cases?
In an application currently in production, one module of code is being modified. Is it
necessary to re- test the whole application or is it enough to just test functionality
associated with that module?
Define each of the following and explain how each relates to the other: Unit, System,
and Integration testing.
Define Verification and Validation. Explain the differences between the two.
Explain the differences between White-box, Gray-box, and Black-box testing.
How do you go about going into a new organization? How do you assimilate?
Define the following and explain their usefulness: Change Management,
Configuration Management, Version Control, and Defect Tracking.
What is ISO 9000? Have you ever been in an ISO shop?
When are you done testing?
What is the difference between a test strategy and a test plan?
What is ISO 9003? Why is it important
What are ISO standards? Why are they important?
What is IEEE 829? (This standard is important for Software Test Documentation-
Why?)
What is IEEE? Why is it important?
Do you support automated testing? Why?
We have a testing assignment that is time-driven. Do you think automated tests are
the best solution?
What is your experience with change control? Our development team has only 10
members. Do you think managing change is such a big deal for us?
Are reusable test cases a big plus of automated testing and explain why.
For more questions-checkout: www.futurethoughtsllc.com
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
Can you build a good audit trail using CPWR's QACenter products. Explain why.
How important is Change Management in today's computing environments?
Do you think tools are required for managing change. Explain and please list some
tools/practices which can help you managing change.
We believe in ad-hoc software processes for projects. Do you agree with this? Please
explain your answer.
When is a good time for system testing?
Are regression tests required or do you feel there is a better use for resources?
Our software designers use UML for modeling applications. Based on their use cases,
we would like to plan a test strategy. Do you agree with this approach or would
this mean more effort for the testers.
Tell me about a difficult time you had at work and how you worked through it.
Give me an example of something you tried at work but did not work out so you had
to go at things another way.
How can one file compare future dated output files from a program which has
change, against the baseline run which used current date for input. The client does
not want to mask dates on the output files to allow compares. - Answer-Rerun
baseline and future date input files same # of days as future dated run of program
with change. Now run a file compare against the baseline future dated output and
the changed programs' future dated output.
Interviewing Suggestions
If you do not recognize a term ask for further definition. You may know the
methodology/term but you have used a different name for it.
Always keep in mind that the employer wants to know what you are going to do for
them, with that you should always stay/be positive.
Preinterview Questions
What is the structure of the company?
Who is going to do the interview-possible background information of interviewer?
What is the employer's environment (platforms, tools, etc.)?
What are the employer's methods and processes used in software arena?
What is the employer's philosophy?
What is the project all about you are interviewing for-as much information as
possible.
For more questions-checkout: www.futurethoughtsllc.com
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
Test Automation:
1. What automating testing tools are you familiar with?
2. How did you use automating testing tools in your job?
3. Describe some problem that you had with automating testing tool.
4. How do you plan test automation?
5. Can test automation improve test effectiveness?
6. What is data - driven automation?
7. What are the main attributes of test automation?
8. Does automation replace manual testing?
9. How will you choose a tool for test automation?
10. How you will evaluate the tool for test automation?
11. What are main benefits of test automation?
12. What could go wrong with test automation?
13. How you will describe testing activities?
14. What testing activities you may want to automate?
15. Describe common problems of test automation.
16. What types of scripting techniques for test automation do you know?
17. What are principles of good testing scripts for automation?
18. What tools are available for support of testing during software development life
cycle?
19. Can the activities of test case design be automated?
20. What are the limitations of automating software testing?
21. What skills needed to be a good test automator?
22. How to find that tools work well with your existing system?
23.Describe some problem that you had with automating testing tool.
24.What are the main attributes of test automation?
25.What testing activities you may want to automate in a project?
26.How to find that tools work well with your existing system?
For more questions-checkout: www.futurethoughtsllc.com
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
Load Testing:
1.What criteria would you use to select Web transactions for
load testing?
2.For what purpose are virtual users created?
3.Why it is recommended to add verification checks to your
all your scenarios?
4.In what situation would you want to parameterize a
text verification check?
5.Why do you need to parameterize fields in your virtual user script?
6.What are the reasons why parameterization is necessary when
load testing the Web server and the database server?
7.How can data caching have a negative effect on load testing results?
8.What usually indicates that your virtual user script has
dynamic data that is dependent on you parameterized fields?
9.What are the benefits of creating multiple actions within
any virtual user script?
General questions:
1. What types of documents would you need for QA, QC, and Testing?
2. What did you include in a test plan?
3. Describe any bug you remember.
4. What is the purpose of the testing?
5. What do you like (not like) in this job?
6. What is quality assurance?
7. What is the difference between QA and testing?
8. How do you scope, organize, and execute a test project?
9. What is the role of QA in a development project?
10. What is the role of QA in a company that produces software?
11. Define quality for me as you understand it
12. Describe to me the difference between validation and verification.
13. Describe to me what you see as a process. Not a particular process, just the
basics of having a process.
14. Describe to me when you would consider employing a failure mode and effect
analysis.
15. Describe to me the Software Development Life Cycle as you would define it.
16. What are the properties of a good requirement?
17. How do you differentiate the roles of Quality Assurance Manager and Project
Manager?
For more questions-checkout: www.futurethoughtsllc.com
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
18. Tell me about any quality efforts you have overseen or implemented. Describe
some of the challenges you faced and how you overcame them.
19. How do you deal with environments that are hostile to quality change efforts?
20. In general, how do you see automation fitting into the overall process of testing?
21. How do you promote the concept of phase containment and defect prevention?
22. If you come onboard, give me a general idea of what your first overall tasks will
be as far as starting a quality effort.
23. What kinds of testing have you done?
24. Have you ever created a test plan?
25. Have you ever written test cases or did you just execute those written by others?
26. What did your base your test cases?
27. How do you determine what to test?
28. How do you decide when you have 'tested enough?'
29. How do you test if you have minimal or no documentation about the product?
30. Describe me to the basic elements you put in a defect report?
31. How do you perform regression testing?
32. At what stage of the life cycle does testing begin in your opinion?
33. How do you analyze your test results? What metrics do you try to provide?
34. Realising you won't be able to test everything - how do you decide what to test
first?
35. Where do you get your expected results?
36. If automating - what is your process for determining what to automate and in
what order?
37. In the past, I have been asked to verbally start mapping out a test plan for a
common situation, such as an ATM. The interviewer might say, "Just thinking out
loud, if you were tasked to test an ATM, what items might you test plan include?"
These type questions are not meant to be answered conclusively, but it is a good way
for the interviewer to see how you approach the task.
38. If you're given a program that will average student grades, what kinds of inputs
would you use?
39. Tell me about the best bug you ever found.
40. What made you pick testing over another career?
41. What is the exact difference between Integration & System testing, give me
examples with your project.
42. How did you go about testing a project?
43. When should testing start in a project? Why?
44. How do you go about testing a web application?
45. Difference between Black & White box testing
46. What is Configuration management? Tools used?
47. What do you plan to become after say 2-5yrs (Ex: QA Manager, Why?)
48. Would you like to work in a team or alone, why?
For more questions-checkout: www.futurethoughtsllc.com
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
4. How much interaction with users should testers have, and why?
5. How should you learn about problems discovered in the field, and what should
you learn from those problems?
6. What are the roles of glass-box and black-box testing tools?
7. What issues come up in test automation, and how do you manage them?
8. What development model should programmers and the test group use?
9. How do you get programmers to build testability support into their code?
10. What is the role of a bug tracking system?
11. What are the key challenges of testing?
12. Have you ever completely tested any part of a product? How?
13. Have you done exploratory or specification-driven testing?
14. Should every business test its software the same way?
15. Discuss the economics of automation and the role of metrics in testing.
16. 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.
17. When have you had to focus on data integrity?
18. What are some of the typical bugs you encountered in your last assignment?
19. How do you prioritize testing tasks within a project?
20. How do you develop a test plan and schedule? Describe bottom-up and top-down
approaches.
21. When should you begin test planning?
22. When should you begin testing?
23. Do you know of metrics that help you estimate the size of the testing effort?
24. How do you scope out the size of the testing effort?
25. How many hours a week should a tester work?
26. How should your staff be managed? How about your overtime?
27. How do you estimate staff requirements?
28. What do you do (with the project tasks) when the schedule fails?
29. How do you handle conflict with programmers?
30. How do you know when the product is tested well enough?
31. What characteristics would you seek in a candidate for test-group manager?
32. 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?
33. How do your characteristics compare to the profile of the ideal manager that
you just described?
34. 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?
35. Who should you hire in a testing group and why?
For more questions-checkout: www.futurethoughtsllc.com
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
36. What is the role of metrics in comparing staff performance in human resources
management?
37. How do you estimate staff requirements?
38. What do you do (with the project staff) when the schedule fails?
39. Describe some staff conflicts youÂ’ve handled.
Here are some questions you might be asked on a job interview for a testing
opening: (from MU COSC 198 Software Testing by Dr. Corliss)
Why did you ever become involved in QA/testing?
What is the testing lifecycle and explain each of its phases?
What is the difference between testing and Quality Assurance?
What is Negative testing?
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?
How would you define Quality Assurance?
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 the Capability Maturity Model (CMM)? At what CMM level were the
last few companies you worked?
What is a "Good Tester"?
Could you tell me two things you did in your previous assignment (QA/Testing
related hopefully) that you are proud of?
List 5 words that best describe your strengths.
What are two of your weaknesses?
What methodologies have you used to develop test cases?
In an application currently in production, one module of code is being modified.
Is it necessary to re- test the whole application or is it enough to just test
functionality associated with that module?
Define each of the following and explain how each relates to the other: Unit,
System, and Integration testing.
Define Verification and Validation. Explain the differences between the two.
For more questions-checkout: www.futurethoughtsllc.com
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
Subscribe to my blog:http://futurethoughtsllc.blogspot.com/
How can one file compare future dated output files from a program which has
change, against the baseline run which used current date for input. The
client does not want to mask dates on the output files to allow compares. -
Answer-Rerun baseline and future date input files same # of days as future
dated run of program with change. Now run a file compare against the
baseline future dated output and the changed programs' future dated output.
Interviewing Suggestions
If you do not recognize a term ask for further definition. You may know the
methodology/term but you have used a different name for it.
Always keep in mind that the employer wants to know what you are going to do
for them, with that you should always stay/be positive.
Preinterview Questions
What is the structure of the company?
Who is going to do the interview-possible background information of
interviewer?
What is the employer's environment (platforms, tools, etc.)?
What are the employer's methods and processes used in software arena?
What is the employer's philosophy?
What is the project all about you are interviewing for-as much information as
possible.
Any terminologies that the company may use.