What you want to see on DotNetFunda.com ?
DotNetFunda.Com Logo
Twitter TwitterLinkedIn
YouTubeGoogle
 Online : 38891 |  Welcome, Guest!   Register  Login
 Home > Interview Questions > Software Testing - Quality Assurance Interview Questions

Now you don't need go anywhere to get the best interview questions on Microsoft technology. We are trying to gather all real interview questions asked from MNCs and put them here. You can also assist us in doing so by submitting .net interview questions. These questions are generally different from certification questions however it may help you in that too.



Page copy protected against web site content infringement by Copyscape
1) Efficiency of developer
2) Efficiency of tester
3) Whether the progress is in gear?

Mean Time Before Failure

Alpha Testing:

A virtual user environment can be created for
this type of testing. Testing is done at the end of
development. Still minor design changes may be made as a
result of such testing.

Beta testing:

Testing is done by end-users or others. Final
testing before releasing application for commercial purpose
is called Beta Testing.

STLC stands for Software Test Life Cycle .

1.Test Planning
Prepare the test plan document, and test cases.

2.Test Development
Preparing requirements documents, UseCase documents, Traceability documents.

3.Test Execution
Executing all Test cases and filling actual results using testing tools and utilities.

4.Result Analysis
Comparing expected results with actual results.

5.Bug Tracking
Filed bugs are identified ,isolated and managed.

6.Reporting
Bug Reporting process, is the reporting of bugs in a database to track further.

Error --> Which comes at the time of development.
Bug --> Which comes at the time of testing. (Pre-Release)
Defect --> Which comes in Production. (Post-Release)

This is the State that is raised when Developer doesn't accept the Bug raised by the QA team !!!

They are many advantages but some of them are :

1. If there are less number of TestCases available then manual testing is the best.

2. Manual Testign allows to perform ad-hock (Random) testing.

3. The Short term costs can be reduced.

4. The more time the Tester spends on Manual Testing the greater the odds to find the real User Bugs .

The rule of a Test Driven Development is to create the test cases prior to writing the actual code. It means that you'll actually be writing code for the tests before you find yourself writing code for the application.


Thanks and Regards
Akiii

nunit.framework.dll

The class library or the application which is doing the testing should add a reference of the above dll


Thanks and Regards
Akiii

NOTE: This is objective type question, Please click question title for correct answer.

NOTE: This is objective type question, Please click question title for correct answer.

Black box testing : This tests are based on requirements and functionality.Internal system design is not considered in this type of testing.

White box testing – This testing is based on knowledge of the internal logic of an application’s code. Also known as Glass box Testing. Internal software and code working should be known for this type of testing. Tests are based on coverage of code statements, branches, paths, conditions

Use cases:
The Use case is made up of a set of possible sequences of interactions between systems and users in a particular environment and related to a particular goal. It will be developed mostly by Business Analyst based on the requirement specification.

Test cases:
Test cases are prepared by testing engineers, based on the Use cases from Functional Requirements Specification (FRS) to check the functionality of the system over the client's perspective. It is a specific set of steps consists of Test Description, Test case ID, Test Category, Actual Result and Expected Result. its main objective is to check the functionality of the system whether its meets the client specification or not.

Group of Test cases are called Test Suite.

NOTE: Based on Use case, Test cases will be written by the testers.

In Software development there are four important steps, also referred to, in short, as the PDCA (Plan, Do, Check, Act) cycle.

Let's review the four steps in detail.

Plan: At this stage, youhave to establish the objectives and processes necessary to deliver results in accordance with the expected output. Clearly describe the goals and policies needed to attain the objective at this stage.

Do/Execute: At this stage, You have to implement the plan, execute the process and then make the product. Finally you have to collect the data from the below Ceck and Act steps.

Check: In this step, you have to study the actual results and compare with the expected output to ascertain any differences.

Act: Finally, you have to analyse the differences to get their route cause. And determine where to apply the changes which includes the improvement of the product.
So developers and other stakeholders of the project do the "planning and building," while testers do the check part of the cycle. Therefore, software testing is done in check part of the PDCA cyle.

Usability testing is a testing methodology where the end customer is asked to use the software to see if the product is easy to use, to see the customer's perception and task time. The best way to finalize the customer point of view for usability is by using prototype or mock-up software during the initial stages. By giving the customer the prototype before the development start-up you confirm that you are not missing anything from the user point of view.

Found this useful, bookmark this page link to the blog or social networking websites. Page copy protected against web site content infringement by Copyscape
Navigate to Page: 1 | 2 | 3 |

 More Exclusive Software Testing - Quality Assurance Interview Questions and Answers here


Found interesting? Add this to:


About Us | Contact Us | The Team | Advertise | Software Development | Write for us | Testimonials | Privacy Policy | Terms of Use | Link Exchange | Members | Go Top
General Notice: If you find plagiarised (copied) contents on this page, please let us know the original source along with your correct email id (to communicate) for further action.
Copyright © DotNetFunda.Com. All Rights Reserved. Copying or mimicking the site design and layout is prohibited. Logos, company names used here if any are only for reference purposes and they may be respective owner's right or trademarks. | 5/21/2013 5:26:36 PM