Knowledge Share

Knowledge is NOT Power IMPLEMENTATION of knowledge is Power!!!
HomePortalGalleryCalendarFAQRegisterUsergroupsLog in



Go down 

Posts : 142
Points : 410
Reputation : 0
Join date : 2007-12-29
Location : Chennai

FAQS3 Empty
PostSubject: FAQS3   FAQS3 Icon_minitimeSat Aug 27, 2011 7:25 pm

Define Bug Life Cycle? What is Metrics?
When we find out the bug, we will put into the “open” status. After fixing the bug developer change the status as “fixed”. Again we will test the fixed part, if there is no bug, change the bug status as “Closed” other wise change the bug status as “Reopen”.
A s/w metric defines the a standard method of measuring certain attributes of the process or the product or the service.

What is the difference between System testing and end to end testing?
System testing is testing conducted on a complete, integrated system to evaluate the system’s compliance with its specified requirements.
end to end testing: here we give real time data…
System Testing: One module or part of the system is tested
end-to-end Testing: The entire project, i.e which has many integrated systems, are tested.

How would you test a fast lazer printer?
-Test for power supply
-pc connection test
-printer sample test
-buffer test
-alignment test
-test for clarity
-speed of printing

Difference between stress testing and load testing?
for all types of applications deny the resources it needs, like: application is developed for 256MB Ram or higher. you test on 64Mb Ram see it fails and fails safely
for client/server applications { 2-tier or higher }
Your request:
5000 users at a time. Check throughput of application, if achieved, load testing for reqd load is done. If not tune the application developed and/or servers
estimating the performance of a application under different load levels.
To estimate the performance of a application when number of concurrent users are accessing at a time.
Estimating the performance of server or CPU by applying max load or peak load.
Estimating the performance of server or CPU under customer expected configuration load is called load testing.
apart from the above information there is more of hardware dependency kind of testing (like: less CPU, less RAM rtc..)
focuses on number of user over a certain peroid of time (like normal users, more than normal user, huge number of users, unbearable number of users etc…)

How to write test cases for a search web page like google?
Test Case No.1
Test Data: Enter the URL of the website and press “Enter button”
Exp Result: Home page of the Website should appears.
Test Case No.2
Test Data: Check all the sub links are enable or disable.
Exp Result: All the sub links must be in enabled state.
Test Case No.3
Test Data: Check whether the Search Button is Enabled or disabled.
Exp Result: Search Button should be in Enabled state.
Test Case No.2
Test Data: Check whether the “search” Text box takes all data or not.
Exp Result: It should take all types of data (like, Numeric,Characters,special Characters etc…).

What is the difference between use case, test case and test plan?
Use Case:

It is prepared by Business analyst in the Functional Requirement Specification (FRS), which is nothing but steps which are given by the customer.
Test cases: It is prepared by test engineer based on the use cases from FRS to check the functionality of an application thoroughly.
Test Plan: Team lead prepares test plan, in it he represents the scope of the test, what to test and what not to test, scheduling, what to test using automation etc.

How can we design the test cases from requirements? Do the requirements, represent exact functionality of AUT?
Yes, requirements should represent exact functionality of AUT.
First of all you have to analyze the requirements very thoroughly in terms of functionality. Then we have to thing about suitable test case design technique [Black Box design techniques like Equivalence Class Partitioning (ECP), Boundary Valve Analysis (BVA),Error guessing and Cause Effect Graphing] for writing the test cases.
By these concepts you should design a test case, which should have the capability of finding the absence of defects.

How to launch the test cases in Test Director and where it is saved?
You create the test cases in the test plan tab and link them to the requirements in the requirement tab. Once the test cases are ready we change the status to ready and go to the “Test Lab” Tab and create a test set and add the test cases to the test set and you can run from there.
For automation, in test plan, create a new automated test and launch the tool and create the script and save it and you can run from the test lab the same way as you did for the manual test cases.
The test cases are sorted in test plan tab or more precisely in the test director, lets say quality centers database test director is now referred to as quality center.

What is the deference between a bug and a defect?
When tester verifies the test cases, all failed test cases are recorded as bugs directed for necessary action and recorded in defected reports. As a testing point of view all fail test cases are defects as well as found bugs. While development point of view if product doesn’t meet the software requirement specifications or any other features that is to be required, it is defect in the system. Who found this feature is not meeting his requirements, he call it is bug in that product.

How can we explain a bug, which may arrive at the time of testing. Explain?
First check the status of the bug, then check whether the bug is valid or not then forward the same bug to the team leader and then after confirmation forward it to the concern developer.

What do you mean by reproducing the bug? If the bug was not reproducible, what is the next step?
Reproducing a bug is as simple as reproducing a defect. If you find a defect, for example click the button and the corresponding action didn’t happen, it is a bug. If the developer is unable to find this behavior he will ask us to reproduce the bug.
In another scenario, if the client complaints a defect in the production we will have to reproduce it in test environment.

How can you know bug is reproducible or not?
A bug is reproducible if we can reproduce it, If we cannot reproduce it, it is not reproducible in which case we will do further testing around it and if we cannot see it we will close it, and just hope it would never come back ever again.

On what basis we give priority and severity for a bug and give one example for high priority and low severity and high severity and low priority?
Always the priority is given by our team leader. Tester will never give the priority.
For example,
High severity: hardware bugs application crash
Low severity: User interface bugs.
High priority: Error message is not coming on time, calculation bugs etc.
Low priority: Wrong alignment, final output wrong.

How is traceability of bug follow?
The traceability of bug can be followed in so many ways.
1. Mapping the functional requirement scenarios (FS Doc) - test cases (ID) - Failed test cases (Bugs)
2. Mapping between requirements (RS Doc) - Test case (ID) - Failed test cases.
3. Mapping between test plans (TP Doc) - test case (ID) - failed test cases.
4. Mapping between business requirements (BR Doc) - test cases (ID) - Failed test cases.
5. Mapping between high level design (Design Doc) - test cases (ID) - Failed test cases.
Usually the traceability matrix is mapping between the requirements, client requirements, function specification, test plan and test cases.

What will be the role of tester if bug is reproduced?
When ever the bug is reproduced, tester can send it back to the developer and ask him to fix it again. If the developer cannot fix the bug once again and if the tester sends the bug back to the developer, the third time the tester can make the bug as deferred i.e. he can reject the build (.exe)

How many functional testing tools are available? What is the easiest scripting language used?
There might be a lot but mostly used are Win runner , silk Test, Rational Robot, QTP These are the functional Testing tools.

What are the types of functional tests available?
There are four types of function to test a system.
1. Functional testing
2. Performance testing
3. integration testing
4. System testing

What is the major difference between Web services & client server environment?
The major difference between them are:
Web Services:
Its more towards the internet side. When we talk about web services it could mean from the java side (deployed on Apache) or Windows side (deployed on IIS). Testing web services is totally a different topic here.
Client Server: The system here involves a client system or a GUI (wherein a user see the front end by which he can input to the system) and a Server ( a backend usually) where in the data gets saved via the GUI.

What is Test Procedure?
Test procedure:-document specifying a sequence of actions for the execution of a particular test. Test Procedure is a part of Test Case document. It comprises of following three steps:
1. To verify the look and feel of AUT through GUI test cases.
2. To verify the positive behavior of AUT through positive test cases.
3. To verify the negative behavior of the AUT through negative test cases.

Key elements of test plan?
The TestPlan consists of so many things. These are Test scope, Test Strategy, Testing Schedule, Resource planning, What to test and What not to test, What can do in manual and What can do in Automation, If Automation then which tool is preferred etc.
Test plan is the plan where, the test lead will select how many testers are required for testing for given application. How to divide the team and test cases. How much time it takes to wind up testing process.

What is SQA testing and steps of SQA testing?
Software QA involves the entire software development PROCESS, monitoring and improving the process. Making sure that any agreed-upon standards and procedures are followed and ensuring that problems are found and dealt with. It is oriented to ‘prevention’. The life cycle begins when an application is first conceived and ends when it is no longer in use. It includes aspects such as initial concept, requirements analysis, functional design, internal design, documentation planning, test planning, coding, document preparation, integration, testing, maintenance, updates, retesting, phase-out, and other specification.

What is the difference between Use Case and Test Case?
Use Case is written in Business Design Document (BDD)by the Business Analyst. It is for understanding the functionality for the person who is involved in writing the test cases.
USE CASE EXAMPLE Action Response
when OK button is clicked Screen 1 appears

Testcase is different perceptions for a functionality to be tested, usually written by a Test Engineer. The same person who has written the testcase may execute them or the other person
Above Usecase is converted into TestCase keeping in mind different perceptions (-ve and +ve)
Action Expected Value Actual Value Result
click on Ok screen 1 should appear(+ve perception) screen1 appeared pass
click on ok screen 2 should appear(-ve perception) screen 1 appeared fail
click on ok screen 2 should appear(-ve perception screen 2 appeared pass
Difference between test case and use case is
use case is prepared by High Level Management team but test case is prepared by
Test engineers.
Use case is prepared for validating the applications in terms of Actors, actions and responses but test case is used to test a specific functionality of an app.

Use case is description of series of events that occur between user and system.
i.e. how system will response when a particular action is taken by user.
Test case:-in use case a generalized scenario is given but in testcase we are more thoroughly testing the various aspect of that generalized scenario.

What is the difference between System testing and end to end testing?
System testing is testing conducted on a complete, integrated system to evaluate the system’s compliance with its specified requirements.
end to end testing: here we give real time data…
System Testing: One module or part of the system is tested
end-to-end Testing: The entire project, i.e which has many integrated systems, are tested.
Back to top Go down
Back to top 
Page 1 of 1

Permissions in this forum:You cannot reply to topics in this forum
Knowledge Share :: Testing :: MANUAL TESTING-
Jump to: