CASE Tool
CASE (computer-aided software engineering) is the use of a computer-assisted method to organize and control the development of software, especially on large, complex projects involving many software components and people. Using CASE allows designers, code writers, testers, planners, and managers to share a common view of where a project stands at each stage of development. CASE helps ensure a disciplined, check-pointed process. A CASE tool may portray progress (or lack of it) graphically. It may also serve as a repository for or be linked to document and program libraries containing the project's business plans, design requirements, design specifications, detailed code specifications, the code units, test cases and results, and marketing and service plans.
CASE originated in the 1970s when computer companies were beginning to borrow ideas from the hardware manufacturing process and apply them to software development (which generally has been viewed as an insufficiently disciplined process). Some CASE tools supported the concepts of structured programming and similar organized development methods. More recently, CASE tools have had to encompass or accommodate visual programming tools and object-oriented programming. In corporations, a CASE tool may be part of a spectrum of processes designed to ensure quality in what is developed. (Many companies have their processes audited and certified as being in conformance with the ISO 9000 standard.)
Some of the benefits of CASE and similar approaches are that, by making the customer part of the process (through market analysis and focus groups, for example), a product is more likely to meet real-world requirements. Because the development process emphasizes testing and redesign, the cost of servicing a product over its lifetime can be reduced considerably. An organized approach to development encourages code and design reuse, reducing costs and improving quality. Finally, quality products tend to improve a corporation's image, providing a competitive advantage in the marketplace.

What is the role of QA in development project?
Deploy and enforce standards
Continually improve standards, QA process based on previous experiences
Promote effective means for reporting and communication.

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

Inspection is a formal evaluation technique in which artifacts are examined in detail by a person or group other than the author to detect errors, violations of development standards, and other problems.

What is Software Review?
Software Review: An evaluation technique that involves the bringing together a group of technical personnel to analyze a software artifact in order to improve its quality.
Review types:
· Informal: adhoc process, no planning, no structure
· Formal (Formal Technical Review): Follow a structured process Produce written report on artifact status Collect and analyze review metrics


What if the application has functionality that wasn't in the requirements?
It may take serious effort to determine if an application has significant unexpected or hidden functionality, and 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. If not removed, design information will be needed to determine added testing needs or regression testing needs. Management should be made aware of any significant added risks as a result of the unexpected functionality. If the functionality only effects areas such as minor improvements in the user interface, for example, it may not be a significant risk.

Security Testing
What is Security Testing?
What is Secure Socket Layer (SSL)? What is does?
What is Firewall?
What is Proxy Server?
What is Digital Certificate and how it is linked to Certificate Authority (CA)?
What is PKI?
What is the difference between HTTP and HTTPS?

What is the difference about web-testing and client server testing?
Web applications are essentially client/server applications - with web servers and 'browser' clients. Consideration should be given to the interactions between html pages, TCP/IP communications, Internet connections, firewalls, applications that run in web pages (such as applets, javascript, plug-in applications), and applications that run on the server side (such as cgi scripts, database interfaces, logging applications, dynamic page generators, asp, etc.). Additionally, there are a wide variety of servers and browsers, various versions of each, small but sometimes significant differences between them, variations in connection speeds, rapidly changing technologies, and multiple standards and protocols. The end result is that testing for web sites can become a major ongoing effort.

Is a “Fast database retrieval rate” a testable requirement?
This is not a testable requirement. ‘Fast’ is a subjective term. It could mean different things depending on a person’s perception. For a requirement to be testable, it should be quantified and repeatable, so that the actual value could be measured against the expected value.

What different type of test cases you wrote in the test plan?
Test cases for interface, functionality, security, load and performance testing.

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.

A typical project may include some or all of the following phases:
· requirements analysis
· functional specifications
· architectural design
· detailed design
· coding
· unit testing
· integration testing
· deployment and
· maintenance.

What are the key challenges of load testing?
The key challenges to load testing is handling various components from various vendors.

Have you done explanatory or specification-driven testing?
Yes, specification-driven testing means checking the product’s confirmance with every statement in every spec, requirements docuement, etc.

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.

What do you like about QA?
QA is the field where in one will be working to multiple environments and can learn more.

Who in the company is responsible for Quality?
Both development and quality assurance departments are responsible for the final product quality.

Should we test every possible combination/scenario for a program?
Ideally, yes we should test every possible scenario, but this may not always be possible. It depends on many factors viz., deadlines, budget, complexity of software and so on. In such cases, we have to prioritize and thoroughly test the critical areas of the application.

What is client-server architecture?
Client-server architecture, a client is defined as a requester of services and a server is defined as the provider of services. Communication takes place in the form a request message from the client to the server asking for some work to be done. Then the server does the work and sends back the reply.

How Intranet is different from client-server?
Internet applications are essentially client/server applications - with web servers and 'browser'

What is three-tier and multi-tier architecture?
A design which separate (1) client, (2) application, and (3) data each into their own separate areas which allows for more scalable, robust solutions

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 user acceptance testing?
It is also called as Beta Testing. Once System Testing is done and the system seems stable to the developers and testers, system engineers usually invite the end users of the software to see if they like the software. If the users like the software the way it is then software will be delivered to the user. Otherwise necessary changes will be made to the software and software will pass through all phases of testing again.

What is manual testing and what is automated testing?
Manual testing involves testing of software application by manually performing the actions on the AUT based on test plans.
Automated testing involves testing of a software application by performing the actions on the AUT by using automated testing tool (such as WinRunner, LoadRunner) based on test plans

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)
· Prototypes.

What is smoke testing?
The smoke test should exercise the entire system from end to end. It does not have to be exhaustive, but it should be capable of exposing major problems. The smoke test should be thorough enough that if the build passes, you can assume that it is stable enough to be tested more thoroughly.

The daily build has little value without the smoke test. The smoke test is the sentry that guards against deteriorating product quality and creeping integration problems. Without it, the daily build becomes just a time-wasting exercise in ensuring that you have a clean compile every day.

The smoke test must evolve as the system evolves. At first, the smoke test will probably test something simple, such as whether the system can say, "Hello, World." As the system develops, the smoke test will become more thorough. The first test might take a matter of seconds to run; as the system grows, the smoke test can grow to 30 minutes, an hour, or more.

What is soak testing?
The software system will be run for a total of 14 hours continuously. If the system is a control system, it will be used to continuously move each of the instrument mechanisms during this time. Any other system will be expected to perform its intended function continuously during this period. The software system must not fail during this period.

What is a pre-condition data?
Data required to setup in the system before the test execution.

What are the different documents in QA?
Requirements Document, Test Plan, Test cases, Test Metrics, Task Distribution Diagrams ( Performance), Transaction Mix, User Profiles, Test Log, Test Incident Report, Test Summary Report

How do you rate yourself in software testing
excellent

What are the best web sites that you frequently visit to upgrade your QA skills?
http://www.softwareqatest.com/
http://sqp.asq.org/

Is defect resolution a technical skill or interpersonal skill from QA view point?
It is a combination of both , because it deals with the interaction with developer either directly or indirectly which needs interpersonal skills and is also based on the skills of the QA personnel to provide a detailed proof to the developer like snap shots and system resource utilization and some suggestions which are little bit technical.

What is End to End business logic testing?
Testing the integration of all the modules of the AUT.

What is an 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 test Metrics?
Test metrics contains follwoing details:
Total test
Test run
Test passed
Test failed
Tests deferred
Test passed the first time

What is the use of Metrics?
Provide the accurate measurement of test coverage.

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?
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?


What is the impact of environment on the actual results of performance testing?
Environment plays an important role in the results and effectiveness of test, particularly in the area of performance testing. Some of the factors will be under our control, while others will not be. These may involve the DBMS, the operating system or the network. Some of the items that we cannot control unless you can secure a stand-alone environment (which will generally be unrealistic) are:
- Other traffic on the network
- Other process running on the server
- Other process running on the DBMS

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 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)

Where do you get your expected results?
User requirement document

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?
Test that need to be run for every build of the application
Tests that use multiple data values for the same actions( data driven tests)
Tests that require detailed information from application internals
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

What is the exact difference between Integration and System testing, give me examples with your project?
Integration testing: An orderly progression of testing in which software components or hardware components, or both are combined and tested until the entire system has been integrated.
System testing: The Process of testing an integrated hardware and software system to verify that the system meets its specified requirements.

How do you go about testing a project?
Analyze user requirement documents and other documents like software specifications, design document etc.
Write master test plan which describe the scope, objective, strategy, risk/contingencies, resources
Write system test plan and detailed test cases
Execute test cases manually and compare actual results against expected results.
Identify mismatches, report defect to the development team using defect reporting tool.
Track defect, perform regression test to verify that defect is fixed and did not disturb other parts of the application.
Once all the defects are closed and application is stabilized, automate the test scripts for regression and performance testing.

How do you go about testing a web application?
We check for User interface, Functionality, Interface testing, Compatibility, Load/Stress, and Security.

Difference between Black and White box testing?
Black box testing: Functional testing based on requirements with no knowledge of the internal program structure or data. Also known as closed-box testing.
White Box testing: Testing approaches that examine the program structure and device test data from the program logic.

What is configuration management? Tools used?
Configuration management: helps teams control their day-to-day management of software development activities as software is created, modified, built and delivered. Comprehensive software configuration management includes version control, workspace management, build management, and process control to provide better project control and predictability

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.

What are the testing tools are you familiar with?
TestDirector, WinRunner, LoadRunner, Rational RequisitPro, Rational TestManager, Rational Robot, Rational ClearQuest and SilkTest.

How did you use automating testing tools in your job?
Automating testing tools are used for preparing and managing regression test scripts and load and perofromenance tests.

What is data-driven automation?
If you want to perform the same operations with differnet set of data, we can create data driven test with loop. In each iteration test is driven by differnet set of data. In order for automation to use data to drive the test, we must subsitute the fixed values in the test with variables.

Describe me the difference between validation and verification?
Verification: typically involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. This can be done with checklists, issues lists, walkthroughs, and inspection meetings.

Validation: typically involves actual testing and takes place after verifications are completed. The term 'IV & V' refers to Independent Verification and Validation

Is coding required in SQA robot?
Yes, to enhance the script for testing the business logic, and when we write the user define the functions.

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.

What are the two ways to copy a file in windows?
1) Using the copy menu item in the edit menu.
2) By dragging the file where ever you want to copy it like a floppy

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.

What is the bug reporting tool used?
Rational ClearQuest
TestDirectror
PVCS Tracker

Did use SQA Manager?
Yes. For creating test plan and defect reporting/tracking.

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.

How do you help developer to track the fault s in the software?
By providing him with details of the defects which include the environment, test data, steps followed etc… and helping him to reproduce the defect in his environment.

Were you able to meet deadlines?
Absolutely.

What is Polymorphism? Give example.
In object-oriented programming, polymorphism refers to a programming language's ability to process objects differently depending on their data type or class. More specifically, it is the ability to redefine methods for derived classes.
For example, given a base class shape, polymorphism enables the programmer to define different circumference methods for any number of derived classes, such as circles, rectangles and triangles.
No matter what shape an object is, applying the circumference method to it will return the correct results. Polymorphism is considered to be a requirement of any true object-oriented programming language (OOPL).

What are the different types of MRs?
MR for suggestions,
MR for defect reports,
MR for documentations changes

What are CMM and CMMI? What is the difference?
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.

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.

Do you have a favorite QA book? Why?
Effective Methods for Software Testing - Perry, William E.

It covers the whole software lifecycle, starting with testing the project plan and estimates and ending with testing the effectiveness of the testing process. The book is packed with checklists, worksheets and N-step procedures for each stage of testing.

When should testing be stopped?
This can be difficult to determine. Many modern software applications are so complex, and run in such an interdependent environment, that complete testing can never be done. Common factors in deciding when to stop are:
- Deadlines (release deadlines, testing deadlines, etc.)
- Test cases completed with certain percentage passed
- Test budget depleted
- Coverage of code/functionality/requirements reaches a specified point
- Bug rate falls below a certain level
- Beta or alpha testing period ends

When do you start developing your automation tests?
First, the application has to be manually tested. Once the manual testing is over and baseline is established.

What are positive scenarios?
Testing to see whether the application is doing what it is supposed to do.

What are negative scenarios?
Testing to see whether the application is not doing what it is not suppose to do.

What is quality assurance?
The set of support activities (including facilitation, training, measurement and analysis) needed to provide adequate confidence that processes are established and continuously improved in order to produce products that meet specifications and fit for use.

What is the purpose of the testing?
Testing provides information whether or not a certain product meets the requirements.

What is the difference between QA and testing?
Quality Assurance is that set of activities that are carried out to set standards and to monitor and improve performance so that the care provided is as effective and as safe as possible. Testing provides information whether or not a certain product meets the requirements. It also provides information where the product fails to meet the requirements.

What are benefits of the test automation?
Fast
Reliable
Repeatable
Programmable
Comprehensive
Reusable

Describe some problems that you had with automation testing tools
One of the problems with Automation tools is Object recognition

Can test automation improver test effectiveness?
Yes, because of the advantages offered by test automation, which includes repeatability, consistency, portability and extensive reporting features.

What are the main use of test automation?
Regression Testing.

Does automation replace manual testing?
No, it does not. There could be several scenarios that cannot be automated or simply too complicated that manual testing would be easier and cost effective. Further automation tools have several constrains with regard the environment in which they run and IDEs they support.

How will you choose a tool for test automation?
OR
How we decide which automation tool we are going to use for the regression testing?
· Based on risk analysis like: personnel skills, companies software resources
· Based on Cost analysis
· Comparing the tools features with test requirement.
· Support for the applications IDE, support for the application environment/platform.

What could wrong with automation testing?
There are several things. For ex. Script errors can cause a genuine bug to go undetected or report a bug in the application when the bug does not actually exist.

How will you describe testing activities?
Testing planning, scripting, execution, defect reporting and tracking, regression testing.

What type of scripting techniques for test automation do you know?
Modular tests and data driven test

What are good principles for test scripts?
Portable
Repeatable
Reusable
Maintainable

What type of document do you need for QA, QC and testing?
Following is the list of documents required by QA and QC teams
Business requirements
SRS
Use cases
Test plan
Test cases

What are the properties of a good requirement?
Understandable, Clear, Concise, Total Coverage of the application

What kinds of testing have you done?
Manual, automation, regression, integration, system, stress, performance, volume, load, white box, user acceptance, recovery.

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.

How do you determine what to test?
Depending upon the User Requirement document.

How do you decide when you have ‘tested enough?’
Using Exit Criteria document we can decide that we have done enough testing.

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 dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. This requires judgment skills, common sense, and experience. (If warranted, formal methods are also available.) 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?
· 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?

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.

What is Black box testing?
Black Box testing is also called system testing which is performed by the testers. Here the features and requirements of the product as described in the requirement document are tested.

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.



What is Regression testing?
Regression testing: Re-testing after fixes or modifications of the software or its environment. It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle. Automated testing tools can be especially useful for this type of testing..

Why do we do regression testing?
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.

How do we regression testing?
Various automation testing tools can be used to perform regression testing like WinRunner, Rational Robot and Silk Test.

What is 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.

What is the difference between exception and validation testing?
Validation testing aims to demonstrate that the software functions in a manner that can be reasonably expected by the customer. Testing the software in conformance to the Software Requirements Specifications.
Exception testing deals with handling the exceptions (unexpected events) while the AUT is run. Basically this testing involves how to change the control flow of the AUT when an exception arises.

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.

What are the roles of glass-box and black-box testing tools?
Glass-box testing also called as white-box testing refers to testing, with detailed knowledge of the modules internals. Thus these tools concentrate more on the algorithms, data structures used in development of modules. These tools perform testing on individual modules more likely than the whole application. Black-Box testing tools refer to testing the interface, functionality and performance testing of the system module and the whole system.

What was the test team hierarchy?
Project Leader
QA lead
QA Analyst
Tester

Which MR tool you used to write MR?
Test Director
Rational ClearQuest.
PVCS Tracker

What are the different automation tools you know?
Automation tools provided by Mercury Interactive - WinRunner, LoadRunner; Rational – Rational Robot; Segue- SilkTest.


What is the role of a bug tracking system?
Bug tracking system captures, manages and communicates changes, issues and tasks, providing basic process control to ensure coordination and communication within and across development and content teams at every step..

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.

Did you ever have problems working with developers?
NO. I had a good rapport with the developers.

Describe your experience with code analyzers?
Code analyzers generally check for bad syntax, logic, and other language-specific programming errors at the source level. This level of testing is often referred to as unit testing and server component testing. I used code analyzers as part of white box testing.

How do you feel about cyclomatic complexity?
Cyclomatic complexity is a measure of the number of linearly independent paths through a program module. Cyclomatic complexity is a measure for the complexity of code related to the number of ways there are to traverse a piece of code. This determines the minimum number of inputs you need to test all ways to execute the program.

Who should test your code?
QA Tester

How do you survive chaos?
I survive by maintaining my calm and focusing on the work.

What Process/Methodologies are you familiar with?
ü Waterfall methodology
ü Spiral methodology
[Or talk about Customized methodology of the specific client]

What you will do during the first day of job?
Get acquainted with my team and application

Tell me about the worst boss you’ve ever had.
Fortunately I always had the best bosses, talking in professional terms I had no complains on my bosses.

What is a successful product?
A bug free product, meeting the expectations of the user would make the product successful.

What do you like about Windows?
Interface and User friendliness
Windows is one the best software I ever used. It is user friendly and very easy to learn.

What is good code?
These are some important qualities of good code
Cleanliness: Clean code is easy to read; this lets people read it with minimum effort so that they can understand it easily.
Consistency: Consistent code makes it easy for people to understand how a program works; when reading consistent code; one subconsciously forms a number of assumptions and expectations about how the code works, so it is easier and safer to make modifications to it.
Extensibility: General-purpose code is easier to reuse and modify than very specific code with lots of hard coded assumptions. When someone wants to add a new feature to a program, it will obviously be easier to do so if the code was designed to be extensible from the beginning.
Correctness: Finally, code that is designed to be correct lets people spend less time worrying about bugs and more time enhancing the features of a program.

Who are Kent Beck, Dr Grace Hopper, and Dennis Ritchie?
Kent Beck is the author of Extreme Programming Explained and The Smalltalk Best Practice Patterns.
Dr. Grace Murray Hopper was a remarkable woman who grandly rose to the challenges of programming the first computers. During her lifetime as a leader in the field of software development concepts, she contributed to the transition from primitive programming techniques to the use of sophisticated compilers.
Dennis Ritchie created the C programming language.

How you will begin improve the QA process?
By following QA methodologies like waterfall, spiral instead of using ad-hoc procedures.

What is UML and how it is used for testing?
The Unified Modeling Language (UML) is the industry-standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems. It simplifies the complex process of software design, making a "blueprint" for construction. UML state charts provide a solid basis for test generation in a form that can be easily manipulated. This technique includes coverage criteria that enable highly effective tests to be developed. A tool has been developed that uses UML state charts produced by Rational Software Corporation's Rational Rose tool to generate test data.