Question: What is the difference between testing and debugging?
Answer: Testing is the performed by tester with the intent of finding a bug in an application. Upon finding a bug, the tester will be reporting it to development team.
Debugging is the act of fixing the bugs that is reported by either the testing team or by the end users. Debugging is done by the development team.
Question: What is difference between Integration testing & Inter system testing?
Answer:
Integration testing: Integrate the all modules and test whether it is functioning correctly or not.
Inter system testing: Testing whether our application/software is supporting the existing software or OS.
Question: What is the difference between SRS and BRS?
Answer: SRS is prepared by Software Analyst. They implement the BRS in preparation of SRS.
BRS is given by Client. It tells the business Logics.
Question: How you prepare Test Data? Is it from Functional Requirements?
Answer: If Functional requirements are available, that means, prior application releases are available, thus best test data comes from it’s operating environment (Production).
Otherwise, create new data to fit the conditions listed in the requirements.
Question: What is the difference between Test Bed and Test Harness?
Answer:
Test Bed: An execution environment configured for testing as hardware, software, networks etc.
Test Harness: A program or test tool used to execute a test it is also known as test driver.
Question: Why do you like to test?
Answer: I like test because I want to give better quality product to my company client and I want to prove the developer can do mistakes I want to find it. So, I like testing.
Question: What is the size of your executable?
Answer: Size of release or size of executable refers to the Kilo line of the code (number of line written for the application is mentioned in the kilo line, we can elaborate this as - E.g. for a module A Total line = (coded line+ commented line +blank line) in which the No. of blank lines can be ignored.
Question: How do you see a QA role in the product development life cycle?
Answer: The roles of QA are as follows:
(A) Preparing Test Strategy
(B) Preparing Test Methodology
(C) Preparing Test Plan
Question: How would you conduct a test: top-down or down-top? What is it? Which one is better?
Answer:
Down-Top: unit -> interface -> system and Top-Down is it’s vice versa. You may use both, but down-top allows discovering malfunctioning at earlier phases of development and cheaper to fix than in the case of top-down.
Question: How would you test a mug (chair/table/gas station etc.)?
Answer: First of all you must demand requirements and functional specification and design document of the mug. There will find requirements like ability to hold hot water, waterproof, stability, break ability and so on. Then you should test the mug according to all documents.
Question: What is the difference between structural and functional testing?
Answer: Structural testing deals with the interior details of the product while the functional testing deals with just the behavior (overview) of the product.
Question: What is the difference between bug priority & bug severity?
Answer: Priority: Urgency Of the Bug.
Severity: Impact of the Bug
Question: What is the testing process?
Answer: Testing the process which ensures that the product will attain the user requirement expectations, as well as it is the process which enables us to find those undiscovered error which can affect the performance of the software product.
Question: What is the Difference between Rational Robot & WinRunner?
Answer: Rational robot is an IBM product and is mainly used for testing the IBM applications. We can build the test cases with in the tool and execute the test cases. Here we can’t synchronize the tests. Here the script generated is SQA/VB script.
WinRunner is a Mercury Interactive product and is used for Functional / regression testing tool.
Here we can’t write the test cases but we can automatically create or manually write the corresponding test script. Here we can synchronize the tests. Here the script generated is test script language (tsl).
Question: What are the steps involved in sanity testing?
Answer: Sanity testing is same as smoke testing. It involves initial testing of the application or module just make sure whether it is stable enough to start testing. Mostly used as a bench mark to gather the readiness of the application for automated testing.
Question: Explain Security testing and Performance testing on Communication interface.
Answer: Security testing is basically done from the access point of view. As all users should not have access to all parts of the application and to the database. For Example end users will have a view of the database they can’t modify or insert any data where as a DBA has all the privileges. Permissions are granted according to the roles of the users at various levels. For major secured applications this testing plays a major role.
Performance testing is done to measure the best utilized CPU time with the best output when concurrent users access the application simultaneously. Depending on the application 50, 100,150…. Users act as end users and start processing the application and compare the outputs obtained.
Question: What is stage containment in testing?
Answer: The defect will be solved at the stage it was found. Advantage of stage containment is it will decrease the cost of quality (coq), if we debug the defect wherever it was found rather finding it in the next stages.
Question: What is Random Testing?
Answer: Random data tests comfort the application under test with input data generated at random. Typically, testers pay no attention to expect data types. They feed a random sequence of numbers, letters & characters into numeric data field.
Question: What is the difference between smoke testing and sanity testing?
Answer:
Smoke testing: This testing is done in post production stage when the application is migrated from QA environment to production environment to check whether its working fine and nothing is broken
Sanity testing: Checking the basic flow of the system like checking all the pages are displayed, all the links are properly working.
Question:
1) How will you write integration test cases?
2) How will you track bugs from WinRunner?
3) How you customize the bugs as pass/fail?
4) You find a bug how will you repair?
5) In test cases you have bug or not?
6) What is use case? What it contains?
Answer:
(1) Integration Testing: Testing of combined parts of an application to determine if they function together correctly. This testing can be performed in both black box and white box testing. The documents like SRS/Functional specifications/Use Cases/Work Flow can be used while deriving integration test cases. We will check the interaction between different units /different functions of an application/product. The format of test case will be almost same for any testing type/technique like test case number, Serial Number, Steps to perform, Test data, Expected, Actual, Status, Priority, Precondition, Created By, Created On, Executed By, and Executed On. We have to divide the features /units where the interaction is possible in the application/product and start writing positive integration test case’s and negative integration test cases. If there is any test data is needed can be derived from equivalence partitioning and boundary value analysis technique and specified in the test data column in the test case.
(2) To track bugs from WinRunner, we need to connect to test director or any defect tracking tool which it supports. From test director we can track the defects from status new to closed.
(3) Defects that are detected should be logged with New Status. After checking the bug the status of that defect changed to open and assigned to a programmer/developer. Developer fixes the bug and assigns back to the tester with fixed status. Here the testing team will validate the defect to know that the defect that is fixed according to the developer is really fixed or not. If the defect is reproducible, its status should be changed to fail and assigned back to the programmer/developer. If the defect is pass, change the status to close. While validating the defect a tester will execute the test case where the defect is found. Still if there is any variation between expected and actual, means defect is reproducible.
(4) Repairing a bug which is found is same as fixing the defect .To fix the defect, a developer will verify the priority and fix accordingly in serial order. For every defect, he will try to reproduce again in developer’s environment. If it is still reproducible, than he will check the code where the defect arises and by his knowledge on the code, he will change the code according to the requirements.
Question: What are the types of functional testing?
Answer: There are following types of functional testing.
1. Functionality testing.
2. Input domain testing.
3. Error handling testing.
(About 90% of the functional testing will be covered with the completion of above three)
4. Recovery testing.
5. Compatibility testing
6. Configuration testing
7. Inter-systems testing
8. Installation testing.
Question: 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?
Answer:
1) Test the modified module
2) Test all the other modules/areas of the application which will have direct/indirect interaction with the modified module.
Question: What test plans have you written?
Answer: Mainly test plan document is prepared by the Test lead or QA lead. The test plan is very important document for the testers, with out test plan tester don’t know what they are going to test, how they are going to do, how much time it will take to test that software.
Question: Who approved your test cases?
Answer: Test lead or we can baseline the test cases with pear reviews and some times client will approve the test cases, that depends on the organization’s policy
Question: How do you know when you have enough test cases to adequately test a software system or module?
Answer: This can be determined by –
1) Risk Analysis of the present system
2) Test Metrics of the previous similar project. If the previous similar project had 100 test cases, which could adequately test the system, and if your present system is 20% enhanced, 130-140 test cases may now do the job.
Question: What is peer review in practical terms?
Answer: A peer review is done during the development stage when x developer develops software his colleague would review the codes for him. It is also known as buddy testing.
Question: How can you know if a test case is necessary?
Answer: �
1) We have to check if the test case is fulfilling the functional requirements or not.
2) In some cases, the test environment makes us to decide if the test case is necessary or not.
Question: If you have an application, but you do not have any requirements available, then how would you perform the testing?
Answer: We can test the application with general assumptions if no requirement doc is available. We can test High severity issues like show stoppers, page crashes, unexpected behavior and etc.
If that is a web application we can go for-
Usability testing — User Friendly ness of the system.
Reliability testing — Whether Active buttons are really active, correct menu options are available, correct hyper links are available
Compatibility testing — Testing the application with different sets of Browser.
Functional testing (if any previous docs are available)
Performance testing
Question: What are all the key factors to write system test plan?
Answer: A system test plan is based on the user requirements document and also the market standards of technology with the most used systems and browsers would be taken into consideration.
Question: What is the Test Server?
Answer: A test server is the server running the application in test. For example we have a LIVE SERVER and TEST server. The proto type of the application would be on the test server and then after testing it would go live on the LIVE server.
Question: What is Difference between QA plan and Test Plan?
Answer:
QA plan: Quality Assurance is the activity performed to prevent the occurrence of errors in the total project. Hence, QA plan specifies the ways to follow to prevent the occurrence of errors in product development.
Test Plan: Testing is the activity performed to prove the conformance of the application to standards. Hence, a test plan specifies the ways to follow to prove the conformance of an application to standards.
Question: What is contained in SRS?
Answer: SRS means software Requirement Specification.
It includes functional requirements to be developed & system requirements to be used.
Question: What is the difference between UAT and system testing?
Answer:
System Testing: Finding the defects, when the system is tested as a whole, this also called as end to end testing. In this testing, tester needs to test the application from log-in to log-out.
UAT: User acceptance testing is to get the acceptance from the client. UAT is generally done at client’s environment. Before UAT pre UAT should be done.
Question: What is bad defect?
Answer: Defect: Of course all Low/Medium/High defects are DEFECTS.
But BAD Defect could be the one comes in higher severity which may affect the crash the system. But the one comes under typo also a defect but never crashes the system.
Question: What is ticketing or error raising process?
Answer: Usually in most of the companies the term ticket is used as synonym for a bug during testing.
So the process of raising an error is called as ticketing. generally whenever a tester encounters a bug during testing he will raise an SFR for that particular bug and against that SFR a brief description will be written as under what conditions or in which scenario that bug has been encountered and the module which is getting affected, assigning the priority and severity for the bug, mentioning the status of the bug and if possible the debug for that particular bug and how to simulate the bug. This entire process is known as the error raising or ticketing process.
Question: If automating - what is your process for determining what to automate and in what order?
Answer: When considering tool support/automation identify all the activities where tool support could be beneficial and priorities them to identify the most important. Although test running tools are the most popular, this may not be the best place to introduce tool support first.
Also consider -
Tool Requirements
CAST readiness
Environment constraints
Tool integration
Job of selecting a suitable test tool should be considered as a process comprising four stages:
* Produce a candidate tool shortlist;
* Arrange demonstrations;
* Evaluate the selected tool(s);
* Review and select tool.
Question: What is the difference between Quality in fact and Quality in perception?
Answer: Quality in fact is quality perceived by the customer’s point of view. it focuses on doing the right things, the right way and on time.
Quality in perception is the supplier’s point of view. it focuses on delivering the right product, satisfying customer needs and treating every customer with integrity courtesy and respect.
Question: What is the difference between CMM & CMMI?
Answer: The Capability Maturity Model (CMM) is a way to develop and refine an organization’s software development process. A maturity model is a structured collection of elements that describe characteristics of effective processes. A maturity model provides:
* A place to start
* The benefit of a community’s prior experiences
* A common language and a shared vision
* A framework for prioritizing actions
* A way to define what improvement means for your organization
* A maturity model can be used as a benchmark for assessing different organizations for equivalent comparison.
The SEI has subsequently released a revised version known as the Capability Maturity Model Integration (CMMI).
Capability Maturity Model® Integration (CMMI) is a process improvement approach that provides organizations with the essential elements of effective processes. It can be used to guide process improvement across a project, a division, or an entire organization. CMMI helps integrate traditionally separate organizational functions, set process improvement goals and priorities, provide guidance for quality processes, and provide a point of reference for appraising current processes.
Benefits of CMMI
* More explicitly link management and engineering activities to their business objectives
* Expand the scope of and visibility into the product life cycle and engineering activities to ensure that the product or service meets customer expectations
* Incorporate lessons learned from additional areas of best practice (e.g., measurement, risk management, and supplier management)
* Implement more robust high-maturity practices
* Address additional organizational functions critical to their products and services
* More fully comply with relevant ISO standards.
Question: What is compliance testing?
Answer: A set of tests carried out to gain sufficient assurance that the prescribed internal controls are operating effectively.
Question: What are entry and exit criteria of a test plan?
Answer: Requirements must be met to move from one phase to another of the SDLC.
A phase cannot be left until exit criteria are met & a phase cannot be entered until entrance criteria is met..
For example: Exit Criteria: Beta stage might begin only when the acceptance test with no bugs found has been completed. I.e. the exit criteria of acceptance test have been met. Similarly for entrance criteria: Formal Spec may be published when the spec review is over & authorized.
Question: In a company if you don’t have hard core written System requirements and the product keep on changing, new features are added without testers knowledge ,in such situation how do you test applications?
Answer: Such situations would normally not arise if a company follows certain standards to maintain quality. Mostly after a certain stage the requirements are locked i.e. they cannot undergo future requirements. Incase such situations arise where it is very important to change the requirement after the specifications have been locked (it’s called Specification complete). It would go through higher authorities who would decide on various factors like if the requirement really needs to be incorporated etc. And if it has to be incorporated it would also lead to various changes in the test plan.
Incase a company doesn’t follow such standard (i.e. specification complete & lock) in that case the customer needs to be highly flexible so does the scheduled date of release of the product needs to be flexible.
Question: What types of tests comes under black box testing
Answer: Black Box testing consists:
1. GUI Testing
2. Load Testing
3. Multi-user/Concurrent Testing
4. Stress Testing
5. Regression Testing
Question: What is FURPS?
Answer: FURPS is the quality Factor for Web Application.
FURPS Stand for -
F - Functionality
U - Usability
R - Reliability
P - Performance
S - Supportability
Question: How will you know whether your reported defect accepted are rejected?
Answer:
1) One will definitely log a defect in Defect tracking tool such as TTpro, Little buggy with status open and assign to respective developer.
2) Status will be new/open once you assign to developer, then he will change the status of defect either fixed/deferred/ and reassign to you.
From status changed by the developer tester will understand his defect has been accepted or rejected.
Question: What is difference between Integration testing & Inter system testing?
Answer:
Integration testing: After the modules (tested units are integrated into modules) are tested, the modules can be integrated and start testing.
Inter system testing: An application which can share same resources with other application is called inter system.
Question: Explain these different approaches of testing a distributed system to me?
- Simulation-based
- Fault Injection-based
- Scenario-based
- Risk-based
- Temporal-based
What are they good for? When to apply each of them?
Answer: �
Scenario based technique: A scenario test normally involves attributes like the test must be realistic. It should reflect something that customers would actually do the test should be complex, involving several features, in a way that should be challenging to the program. It should be easy and quick to tell whether the program passed or failed.
A stakeholder is likely to argue vigorously that the program should be fixed if it fails this test. Tests derived from use cases are also called scenario test.
Question: In bug life cycle which what are the activities between new and assigned states
Answer: NEW means when a tester will find a defect he/she will mark it as only NEW as this defect has found now and he/she will send it to T.L and D.L
ASSIGN means after getting a Bug from testing Engineer ( which is marked as NEW ) the D.L will verify it whether it is proper to Fix or not. if after verify all the criteria the D.L has agreed to accept that bug for fixing then he will “ASSIGN” that to the bug related Developer.
Question: What is the difference between authorization and authentication?
Answer:
Authentication: An authentication system is how you identify yourself to the computer. The goal behind an authentication system is to verify that the user is actually who they say they are.
Authorization: Once the system knows who the user is through authentication, authorization is how the system decides what the user can do.
Question: How can you take snapshot/screen shots in case of manual testing and how can you attach it to the test case?
Answer: Use print screen button and paste it in paint. Attach against the specific test case in the comments column or if you are using test director or Bugzilla, we have a field as attachment.
Question: Is retesting is a part of regression testing or regression testing is a part of retesting?
Answer: Technically there is no concept of Retesting, but some how it is used in testing world. Retesting is process of repetition of old test cases.
Regression testing is done when there is change in software i.e. Defect has been fixed, New functionality is added or deleted. We compare newer version with older version.
Question: What is V&V concept?
Answer: V&V concept is representation of V- Model which talks about Verification and Validation. Left side of V-model called verification ( Requirement analysis , Specification, Design, Implementation) Right side of V-model called Validation ( Unit testing , integration testing , system testing, User acceptance testing)
Question: What do you mean by Masked Defect?
Answer: An existing defect that hasn’t yet caused a failure because another defect has prevented that part of the code from being executed is called Masked Defect.
Question: If an application has 100 pages to be tested. How much time it will take?
How you will calculate? (It Depends upon the Complexity of the functionality is know factor)
Answer: The time taken for completion of an application will me measured using Cyclomatic Complexity. It is a quantitative measure to calculate time.
Question: What is the basic stuff you require to begin creating test cases?
Answer: Basic stuff requires for Test cases is full fledge knowledge of Functional design and STLC. Scenario plays a vital role for having Test Cases.
Question: What are the tables in test plans and test cases?
Answer: Test plan is a document that contains the scope, approach, test design and test strategies. It includes the following:-
1) Test case identifier
2) Scope
3) Features to be tested
4) Features not to be tested.
5) Test strategy.
6) Test Approach
7) Test Deliverables
Responsibilities.
9) Staffing and Training
10) Risk and Contingencies
11) Approval
While a test case is a noted/documented set of steps/activities that are carried out or executed on the software in order to confirm its functionality/behavior to certain set of inputs.
Test cases contains -
1) Serial number.
2) Title
3) Test description
4) Test data
5) S/p basis
6) Expected and actual result
7) Remarks
Question: What are merits and demerits of white box and black box testing?
Answer: Testing a function with knowing the internal structure it also call as white box testing it takes place in the developer’s area.
Question: What is Cyclomatic complexity?
Answer: The Cyclomatic complexity is software metric that provides a quantitative measure of the logical complexity of a program.
What people said