Source: The following definitions are taken from GLOSSARY OF COMPUTERIZED SYSTEM AND SOFTWARE
DEVELOPMENT TERMINOLOGY
audit. (1) (IEEE) An independent examination of a work product or set of work products to assess compliance
with specifications, standards, contractual agreements, or other criteria. See: functional configuration audit,
physical configuration audit. (2) (ANSI) To conduct an independent review and examination of system records
and activities in order to test the adequacy and effectiveness of data security and data integrity procedures, to
ensure compliance with established policy and operational procedures, and to recommend any necessary
changes. See: computer system audit, software audit. More . . .
Software Testing Life Cycle consists of six (generic) phases:
Test Automation job interview questions:
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? More . . .
Software testing is probably the most complex task in the software development cycle. It
often takes longer to test the software than it does to write the code. The problems
discovered during the software testing phase add more time onto the coding phase,
resulting in further delays in the product’s release, and so this vicious cycle goes.
It’s nearly impossible to attribute the problems that arise during the software testing
cycle to any single factor. Before going any further, it’s important to clarify one More . . .
1. The Software Life Cycle
An introduction to the fundamental elements of the software life cycle, and several life cycle
models that are commonly in use. Also, how testing is integrated into the life cycle.
a. Life cycle models
b. Types of testing and where they fit in
i. Unit Testing
ii. Regression Testing
iii. Integration Testing
iv. System Testing More . . .
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.
Why you write MR?
MR is written for reporting problems/errors or suggestions in the software.
What information does MR contain?
OR
Describe me to the basic elements you put in a defect report? More . . .
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 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: More . . .
What is White box testing/unit testing?
Unit testing – The most ‘micro’ scale of testing; to test particular functions or code modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done unless the application has a well-designed architecture with tight code; may require developing test driver modules or test harnesses.
What is Integration testing?
Integration testing – Testing of combined parts of an application to determine if they function together correctly. The ‘parts’ can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems. More . . .
URS—User Requirement Specification
SRS– System Requirement Specification
Explain the software development lifecycle.
There are seven stages of the software development lifecycle
• Initiate the project – The users identify their Business requirements.
• Define the project – The software development team translates the business requirements into system specifications and put together into System Specification Document. More . . .
