Interview Questions Part 2

-->

Q.  What is a Risk? What are the important components of the risk?

A. Risk is a condition that will result in loss.
The important components of risk are a) Probability the risk will occur b) Impact of the risk c) Frequency of occurrence

Q.  What is walkthrough and inspection?                 

A. Walkthrough is there for both Testing and Coding.
Walkthrough for testing means brief review of documents, Test cases, Test script etc.
Walkthrough for Coding means review the coding for whether the Developer follows the Coding standards or not.

Inspection is job of Quality Control (QC). He can conduct Inspections and Audits on the project at any time to check whether the process is going on correctly or not.
I will tell y one example for Test Engineer, QA, QC
Take an Examination Center: In that

• Test Engineer is Examiner
• QA is sitting squad
• QC is a flying squad

Q. What is Release Acceptance Testing?
What is Forced Error Testing?
What is Data Integrity Testing?
What is System Integration Testing

A.  Following are the details regarding Release Acceptance Testing, System Integration Testing, Data Integrity Testing

1. Release Acceptance Testing
Lets consider the following example:
The business says a bank plans to plan to test a cards application in 3 releases: Release 1, 2 & 3.
Each release has few enhancements (functionalities) like Chargeback’s, Fraud reporting etc.,
Testing these enhancements release wise is termed as Release Acceptance Testing

2. System Integration Testing
Clubbing all the modules of an application together and testing it as one single system is termed as System Integration Testing

3. Data Integrity Testing
Consider the scenario below:
When some external data (like Flat Files) are transmitted into to your application you expect complete communication of data (say for example if you are expecting Rs.5000/- from the external file to be populated as Rs.5000/- in Transaction Amount field in your application then you are looking out for Integrity of data transferred from external interface to your application. This is Data Integrity Testing
No idea about Forced Error Testing.

Q.  What is the Compatibility testing difference between testing in IE explorer and testing in Firefox?

A. In IE we can look perfectly the web pages where as in Firefox some images and text are not displayed properly

Q.  How do u conduct boundary analysis testing for "ok" pushbutton?

A. There is no boundary value analysis for "Ok" Push-Button.

Q. What is the strength and weakness in testing?

A. Strength: Judgeemnt skills, patience, pessimistic in nature, strong desire quality Weakness: like, i love coffee so i drink coffee every hour

Q.  What do we do when there is a known bug at the time of software release?

A.  If there is any open bug at the time of release we mention in the release note which we send with the release, in open list of issues. As we know if client finds that we have mentioned the issue in release note he will not be worried about the type of testing being done on the application. But if he himself finds that bug it will hurt our company image.

Q.  What is "bug leakage?" and what is "bug release?"

A. The bugs un discovered in the previous stage / cycles is called bug leakage for that stage/cycle. Eg. Suppose you have completed System Testing (ST)
and certified the application as fully tested and send it for UAT. but UAT certainly uncovers some of the bugs which are not found at ST stage. so bugs are leaked from ST stage to UAT. this is called bug leakage.

Q.  Which of the following statements about regression testing are true?
(1) Regression Testing must consist of a fixed set of tests to create a baseline
(2) Regression Testing should be used to detect defects in new features
(3) Regression Testing can be run on every build
(4) Regression Testing should be targeted to areas of high risk and known code change
(5) Regression Testing, when automated, is highly effective in preventing defects

A.  1 4 and 5 are correct

Q. How can we perform testing without expected results?

A. Main concept in testing is the expected result. By knowing the expected behavior of the application or system from SRS and FDS, we can derive a test case. When executed the derived test cases, actual result is noted. Any deviation from the expected is considered as a defect.

In Adhoc testing, there is no need of a test case, but if we want to log a defect, we should know the expected behaviour of the application or a system.

There is only one possibility for this question according to me. Exploratory testing.
An interactive process of concurrent product exploration, test design, and test execution. The heart of exploratory testing can be stated simply. The outcome of this test influences the design of the next test. Tester will explore the product or application and will note down the expected result and will design a test case and execute the test.

Q. What is defect leakage?

A. If any defect which we could not find out in system test environment then it is called as defect leakage.

Q. What are the parameters of Quality cost?

A.  Quality cost or Cost of quality depends on the time factor that is at what time the bug is detected. If the bug is detected at the time of release then the cost of quality will increase & if the bug is detected at requirement phase then the cost of quality will be very less. So the conclusion is the main parameter of Quality cost is "Time at which bug is detected".

Q. Could we test window's calculator through win runner. for e.g. if I have to show get the value of calculator buttons.

A. yes, we can test the window's calculator using win Runner and also you can show the values of buttons.

Q. What is SQA Activities?

A. SQA activities - suggesting & reviewwing the process docuemtents
Example - reviewing project management plan, etc

Q.  What is the difference in writing the test cases for Integration testing and system testing

A. Integration Testing:
Mostly the integration Testing is not done by Test Engineer.
Integration testing test case includes a partial amount of the conditions used for system testing.
System testing = Functionality Testing + Integration + Unit (Complete round of testing)

Q. What is a deliverable ? Can you please mention the names of deliverables in your current project .

A. Test Deliverables:-
1.Test plan document
2.Test case document
3. Test strategic document
4.test script document
5.test scenario document
6.test log document
7.coding guidlines document
8. automation procedure document

Q. What metrics used to measure the size of the software?

A.  There are 4 ways in which u can measure the program size1)Lines of code i.e.LOC2)Function points3)McCabe's complexity metric which is the number of decisions(+1) in a program4)Halstead's metrics that are used to calculate program length

Q.  Let us know your understanding of Audits ?

A. Audit comes under QA. Its a checking of the processes in the organistion which are define are followed by the employee.
In this every product is audited for the process, that its going as per the organistion's define process or not. Reviwing the documents, matrix related to the product are checked.

Q.  What are the contents of Risk management Plan? Have you ever prepared a Risk Management Plan ?

A.  In general it consist of types risk associated and mitigation for it. It also consist of severity. In general RMP is created by PM and updated by Module Leads when needed.

Q. How can you say your project testing is completed? Explain the various factors?

A.  There are so many factors to know this answer.. some main factors are.....
1) Dead line of your Project reaches
2) Your Estimated Budget over.
3) Acives Customer's Requirement with certain percentage of test case passed.
etc......

If you have any quarries/feed back send me on - knowthetesting@gmail.com

Thank you

Ram

Interview Questions Part 1

Q. Give me full explanation for SDLC process.

A. SDLC means Software Development Life Cycle.
In this approach following activities are carried out.
1. Requirements gathering
2.  Analysis and planning

3.  Design

4.  Coding

5. Testing

6. Maintenance

In this approach testing comes into picture after coding and conducted by same development people. Testing can be have a place in any of these stage depends on the Development Models.

Q.  What is the testing life cycle?

A. There is no standard, but it consists of:
Test Planning (Test Strategy, Test Plan(s), Test Bed Creation)
Test Development (Test Procedures, Test Scenarios, Test Cases)
Test Execution
Result Analysis (compare Expected to Actual results)
Defect Tracking
Reporting

OR

I have done some modification in the above answer , please find below the same :
Test Life Cycle :
1. Test Plan :
a)Test Scope
b)Test Strategy
c)Test scheduling
d)Test Estimation
e)Test Bed Creation
f)Test Techniques
2. Test Development:
a)Test Scenarios
b)Test Case Authoring
3. Test Execution
4. Result Analysis ( comparing the expected and actual result)
5.Defect Tracking -->
a)Filing of new defect
b)Verification of defect
c)closure of defect
6.Test Regression
7.Test Stop.

Q.  Difference between Configuration Management and Version Control.

A. Version Control is part of Configuration Management.
Read the following, you will understand.

Configuration Management is the approach used in managing the individual components (software & hardware) that make up the? System? It is important not to confuse ? Configuration Management?  with ? Change Management?
Change management is concerned with changes made to an item/s. Whereas Configuration Management is concerned with managing all of the individual items, and all of the items as a whole (System).

Software exists in two forms; non-executable (source code) and executable code (object code). When errors are found in the software, changes may be required to be made to the source code. When this situation occurs, it is imperative to be able to identify which version of code to change. There may also arise a situation where two Developers need to make changes to the code. If the Developers are unaware of the other updating the version, then both updated versions could be saved causing lost changes or worse. Also, Testers may not be aware of which version of code to test with causing further problems.

When testing is complete, a Test Leader will need to demonstrate that the testing has been completed on a specific version of code, a necessity to ensure correct test coverage.

It is not only software and hardware components that need to be controlled, but also documentation, as project members will need to ensure they work from the correct versions.

Configuration Management consists of the following four parts:
Configuration Identification
Configuration Control
Status Accounting
Configuration Auditing
Configuration Identification
This is the process of identifying all of the individual items that will be subject to version control within the project. Details such as version and status may be recorded.

Configuration Control
This activity ensures that any changes are controlled and monitored. A master copy should be kept in order for people to be able to check out the latest version of the document to avoid two people working on the same document version. Items such as ?dates?, ?version numbers? and ?updated by? are details that may be recorded. Once the item has been updated, the item can be checked back in, resulting in it becoming the master copy. A history will be displayed when multiple versions exist.
Status Accounting
this is the process of recording and reporting on the current status of the item. It is in effect the ability to be able to view the current state of the item.
Configuration Auditing
Configuration Auditing is used to ensure that the control process that is used is being correctly adhered to

Q.  How do you ensure the quality of the product?

A. The quality of the product can be ensure by look into the minimum bugs in a products as per the standard maintained by the organization for the clients. That means if a company is the six sigma oriented company then there should be at least  3-4 bugs per millions.

Q. What if there isn't enough time for thorough testing?

A. 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.

Use risk analysis to determine where testing should be focused. This requires judgment skills, common sense and experience. The checklist should include answers to the following questions:
* 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?

Q. What's normal practices of the QA specialists with perspective of software?

A. These are the normal practices of the QA specialists with perspective of software
[note: these are all QC activities, not QA activities.]
1-Desgin Review Meetings with the System Analyst and If possible should be the part in Requirement gathering
2-Analysing the requirements and the desing and to trace the desing with respect to the requirements
3-Test Planning
4-Test Case Identification using different techniques (With respect to the Web Based Applciation and Desktoip Applications)
5-Test Case Writing (This part is to be assigned to the testing engineers)
6-Test Case Execution (This part is to be assigned to the testing engineers)
7-Bug Reporting (This part is to be assigned to the testing engineers)
8-Bug Review and thier Analysis so that future bus can be removed by desgining some standards

Q. What is the difference between high level design and low level design?

A. Every software design is presenting with one high level design and one low level design.Because high level design is a system level document and low level desings are functionalise and modules level documents.

OR

High Level Document and Low Level Document are comes under Software Requirement Specifications (SRS). It comes under the Design phase which is in SDLC.

High Level Documents are design documents wat exactly meaning is what the customer wants this comes under HLDD.

Low Level Documents in this we have in which way client wants the application and describes about the procedures and sub routins and basic documents.

Q. What is the difference between Quality Assurance and Quality Control?

A. Quality assurance is set of activitates designed to ensure that maintenance process is adequate to ensure a system will meet it object.
Quality control is set of activitates designed to evaluate a developed work product

OR

Quality Assurance deals with Monitoring and Improving entire SDLC.
Quality Control(QC) deals with Walkthroughs, Reviews and Inspection.

If you have any quarries/feed back send me on - rampeddireddy2006@gmail.com, ram@examsinfo.in.

Thank you

Ram

Software testing questions and answers

This article is the part software testing question and answer series. If you have queries on software testing, quality assurance or career in testing then you can ask me these questions in comment section below.

With reference - www.softwaretestinghelp.com

Naresh A. asks:

“My past experience was related to “Test Engineer”. Recently I am appointed as Test Lead in a product based company. Currently there is no Pre-established testing process. As a TL am meant to define a standard process for the entire testing flow and I will maintain certain documents for each product.

Can you help me out in establishing a process for testing, and make me know the entire responsibilities of TL and what documents I am supposed to prepare and maintain?”

As a team leader you are responsible for project planning, scheduling, and communicating your project status to your manager and most important task of assigning and monitoring the project work. Your main responsibility is to build a team to achieve your project goals. You need to focus on handling the challenges in your project so that your team and project will grow and perform well.

As far as the standard testing process is considered, it’s depends on you - what procedure you want to establish. Yes some people might blame me for this point but I prefer to establish my own processes that work for me. I don’t stick to those old process definitions that are written and managed in some 90’s and most of which might not applicable nowadays.

Test lead is responsible for ensuring project plan changes are incorporated in test plan. You might write a test plan and test strategy (In some cases it might be written by senior test team member or even by project test manager) Ensure the work is going according to this test plan. Identify the risks and try to mitigate them. At the end of project testing life cycle ensure that all test objectives are accomplished and acceptance criteria is met.

More TL responsibilities includes: Test Case Review, Requirements Validation, Monitoring the execution of manual and automated test cases, Prepare test summary report and Communicate test status to seniors and prepare corresponding documents.

To know more on SQA processes read this article “SQA Processes- How to Test complete application“. Hope from this answer you will get good idea of testing processes and TL responsibilities.

Pavan Ankus asks:

“I am appearing for the QA positions in US. I would kindly request you to mail me the suitable challenging situations in manual testing and also since I don’t have domain knowledge in Insurance, finance and other financial domain experience I am finding hard to explain to the interviewer as an experienced person. In this regard I need your suitable answer as to how to face the interviewer?”

In every testing interview you will get this question: “Tell me any challenging situation you faced in your previous projects or Tell me any bug that you feel proud to find it?”

I think answers to these questions depend on your testing career. I know every one of you might have faced many challenging situations where exceptional thinking is required to solve such problems.

I will suggest to pick any such situation from you career and explain it in better way. At least it should sound challenging This will help you to face further questions from interviewer depending on your answer.

The broad challenges in manual testing are: How to ensure complete test coverage? Testing without an automation tool is itself a big challenge. You can also explain non-technical challenges in manual testing like managing the testing work in critical time (Llink to testing under time limit) i.e. completing testing before deadline and even worst case if the deadline itself is not feasible.

Explaining a challenging bug you found in your career can be also a good answer for this question. For example the bug that was difficult to find or reprove or having big impact on customer revenue etc.

Pavan you mentioned that you don’t have knowledge in banking and finance domain then how you expect from yourself to give answer on that? If you don’t have experience in banking and finance domain then do not put this as a skill in your resume just for the sake of matching your profile with employer requirements. If you really want to get into testing of BFSI (Banking, Financial services and Insurance) domain then first study this domain. Know the basic concepts in BFSI domain. See the resources I have listed on BFSI domain on our resource page. Keep in mind you can answer in detail about any question if you have worked on that.

Mitch asks:

“What is the best way to go about getting a pay rise? Is reporting and graphing bugs found compared to other team member a good idea?

Comparing the bug count with other team or team member is very bad idea to ask for pay rise. If you are working for the organization for long time then your employer know your value and importance in organization. There is no need to show how your bug count graph is higher than your counterparts.

So what is the best way to ask for good salary rise?

At the time of your performance appraisal you should be able to convince to your reviewer that how you worked hard for your organization, How you succeeded in managing difficult tasks and how you enhanced your skills to better match your current work profile. If you succeed in this negotiation then you will definitely get good pay rise.

Other factors considered while giving you pay rise:

Your relevant skills, Complexity of application you are working on, problem solving skill, total and relevant experience, education and certifications.

If you have any quarries/feed back send me on - rampeddireddy2006@gmail.com, ram@examsinfo.in.

Thank you

Ram