1. What is meant by Priority and
severity?
Severity:
1. This is assigned by the Test Engineer
2. This is to say how badly the deviation that is occurring is affecting the other modules of the build or release.
Priority:
1. This is assigned by the Developer.
2. This is to say how soon the bug as to be fixed in the main code, so that it pass the basic requirement.
Egg. The code is to generate some values with some valid input conditions. The priority will be assigned so based on the following conditions:
a> It is not accepting any value
b> It is accepting value but output is in non-defined format (say Unicode Characters).
A good example I used some Unicode characters to generate a left defined arrow, it displayed correctly but after saving changes it gave some address value from the
Stack of this server. For more information mail me I will let you know.
1. This is assigned by the Test Engineer
2. This is to say how badly the deviation that is occurring is affecting the other modules of the build or release.
Priority:
1. This is assigned by the Developer.
2. This is to say how soon the bug as to be fixed in the main code, so that it pass the basic requirement.
Egg. The code is to generate some values with some valid input conditions. The priority will be assigned so based on the following conditions:
a> It is not accepting any value
b> It is accepting value but output is in non-defined format (say Unicode Characters).
A good example I used some Unicode characters to generate a left defined arrow, it displayed correctly but after saving changes it gave some address value from the
Stack of this server. For more information mail me I will let you know.
2. Give me some example for high
severity and low priority defect?
If suppose the title of the particular concern is not spelled correctly, it would give a negative impacted ICICC is spelled as a title for the project of the concern ICICI. Then it is a high severity, low priority defect.
If suppose the title of the particular concern is not spelled correctly, it would give a negative impacted ICICC is spelled as a title for the project of the concern ICICI. Then it is a high severity, low priority defect.
3. What is basis for test case
review?
The main basis for the test case review is
1. Testing techniques oriented review
2. Requirements oriented review
3. Defects oriented review.
The main basis for the test case review is
1. Testing techniques oriented review
2. Requirements oriented review
3. Defects oriented review.
4. What are the contents of SRS
documents?
Software requirements specifications and Functional requirements specifications.
Software requirements specifications and Functional requirements specifications.
5. What is difference between the Web application testing
and Client Server testing?
Testing the application in intranet (without browser) is an example for client -server. (The company firewalls for the server are not open to outside world. Outside people cannot access the application.)So there will be limited number of people using that application.
Testing an application in internet (using browser) is called web testing. The application which is accessible by numerous numbers around the world (World Wide Web.)
So testing web application, apart from the above said two testing there are many other testing to be done depending on the type of web application we are testing.
If it is a secured application (like banking site- we go for security testing etc.)
If it is an e-commerce testing application we go for Usability etc…Testing.
Testing the application in intranet (without browser) is an example for client -server. (The company firewalls for the server are not open to outside world. Outside people cannot access the application.)So there will be limited number of people using that application.
Testing an application in internet (using browser) is called web testing. The application which is accessible by numerous numbers around the world (World Wide Web.)
So testing web application, apart from the above said two testing there are many other testing to be done depending on the type of web application we are testing.
If it is a secured application (like banking site- we go for security testing etc.)
If it is an e-commerce testing application we go for Usability etc…Testing.
6. Explain your web application
architecture?
Web application is tested in 3 phases
1. Web tier testing –> browser compatibility
2. Middle tier testing –> functionality, security
3. Data base tier testing –> database integrity, contents
Web application is tested in 3 phases
1. Web tier testing –> browser compatibility
2. Middle tier testing –> functionality, security
3. Data base tier testing –> database integrity, contents
7.suppose the product/application has
to deliver to client at 5.00PM,At that time you or your team member caught a
high severity defect at 3PM.(Remember defect is high severity)But the client is
cannot wait for long time. You should deliver the product at 5.00Pm exactly.
Then what is the procedure you follow?
The bug is high severity only so we send the application to the client and find out the severity is priority or not. If its priority then we ask him to wait.
Here we found defects/bugs in the last minute of the delivery or release date
Then we have two options
1. Explain the situation to client and ask some more time to fix the bug.
2. If the client is not ready to give some time then analyze the impact of defect/bug and try to find workarounds for the defect and mention these issues in the release notes as known issues or known limitations or known bugs. Here the workaround means remedy process to be followed to overcome the defect effect.
3. Normally this known issues or known limitations (defects) will be fixed in next version or next release of the software
The bug is high severity only so we send the application to the client and find out the severity is priority or not. If its priority then we ask him to wait.
Here we found defects/bugs in the last minute of the delivery or release date
Then we have two options
1. Explain the situation to client and ask some more time to fix the bug.
2. If the client is not ready to give some time then analyze the impact of defect/bug and try to find workarounds for the defect and mention these issues in the release notes as known issues or known limitations or known bugs. Here the workaround means remedy process to be followed to overcome the defect effect.
3. Normally this known issues or known limitations (defects) will be fixed in next version or next release of the software
8. Give me examples for high priority
and low severity defects?
Suppose in one banking application there is one module ATM Facility. In that ATM facility when ever we are depositing/withdrawing money it is not showing any conformation message but actually at the back end it is happening properly with out any mistake means only missing
Of message. In this case as it is happening properly so there is nothing wrong with the application but as end user is not getting any conformation message so he/she will be
Confuse for this. So we can consider this issue as HIGH Priority but LOW Severity defects…
Suppose in one banking application there is one module ATM Facility. In that ATM facility when ever we are depositing/withdrawing money it is not showing any conformation message but actually at the back end it is happening properly with out any mistake means only missing
Of message. In this case as it is happening properly so there is nothing wrong with the application but as end user is not getting any conformation message so he/she will be
Confuse for this. So we can consider this issue as HIGH Priority but LOW Severity defects…
9. Explain about Bug life cycle?
1) Tester->
2) Open defect->
3) Send to developer
4) ->if accepted moves to step5 else sends the bug to tester gain
5) Fixed by developer ->
6) Regression testing->
7) No problem inbuilt and sign off
->if problem in built reopen the issue send to step3
1) Tester->
2) Open defect->
3) Send to developer
4) ->if accepted moves to step5 else sends the bug to tester gain
5) Fixed by developer ->
6) Regression testing->
7) No problem inbuilt and sign off
->if problem in built reopen the issue send to step3
10. How can you report the defect
using excel sheet?
To report the defect using excel sheet
Mention: The Future that been effected.
Mention: Test Case ID (Which fail you can even mention any other which are dependency on this bug)
Mention : Actual Behavior
Mention : Expected Behavior as mentioned in Test Case or EFS or EBS or SRS document with section
Mention : Your Test Setup used during Testing
Mention : Steps to Re-Produce the bug
Mention : Additional Info
Mention : Attach a Screen Shot if it is a GUI bug
Mention : Which other features it is blocking because of this bug that you are unable to
Execute the test cases.
Mention: How much time you took to execute that test case or follow that specific TC
Which leaded to bug?
To report the defect using excel sheet
Mention: The Future that been effected.
Mention: Test Case ID (Which fail you can even mention any other which are dependency on this bug)
Mention : Actual Behavior
Mention : Expected Behavior as mentioned in Test Case or EFS or EBS or SRS document with section
Mention : Your Test Setup used during Testing
Mention : Steps to Re-Produce the bug
Mention : Additional Info
Mention : Attach a Screen Shot if it is a GUI bug
Mention : Which other features it is blocking because of this bug that you are unable to
Execute the test cases.
Mention: How much time you took to execute that test case or follow that specific TC
Which leaded to bug?
11. If you have executed 100 test
cases , every test case passed but apart from these test case you found some
defect for which test case is not prepared, then how you can report the bug?
While reporting this bug into bug tracking tool you will generate the test case mean put the steps to reproduce the bug.
While reporting this bug into bug tracking tool you will generate the test case mean put the steps to reproduce the bug.
12. What is the difference between
web based application and client server application?
The basic difference between web based application & client server application is that the web application are 3 tier & client based are 2 trier. In web based changes are made at one place & it is reflected on other layers also whereas client based separate changes need be installed on client machine also.
The basic difference between web based application & client server application is that the web application are 3 tier & client based are 2 trier. In web based changes are made at one place & it is reflected on other layers also whereas client based separate changes need be installed on client machine also.
13. What is test plan? And can you
tell the test plan contents?
Test plan is a high level document which explains the test strategy, time lines and available resources in detail. Typically a test plan contains:
-Objective
-Test strategy
-Resources
-Entry criteria
-Exit criteria
-Use cases/Test cases
-Tasks
-Features to be tested and not tested
-Risks/Assumptions.
Test plan is a high level document which explains the test strategy, time lines and available resources in detail. Typically a test plan contains:
-Objective
-Test strategy
-Resources
-Entry criteria
-Exit criteria
-Use cases/Test cases
-Tasks
-Features to be tested and not tested
-Risks/Assumptions.
14. How many test cases can you write
per a day, an average figure?
Complex test cases 4-7 per day
Medium test cases 10-15 per day
Normal test cases 20-30 per day
Complex test cases 4-7 per day
Medium test cases 10-15 per day
Normal test cases 20-30 per day
15. Who will prepare FRS (functional
requirement documents)? What is the important of FRS?
The Business Analyst will pre pare the FRS.
Based on this we are going to prepare test cases.
It contains
1. Over view of the project
2. Page elements of the Application (Filed Names)
3. Prototype of the of the application
4. Business rules and Error States
5. Data Flow diagrams
6. Use cases contains Actor and Actions and System Responses
The Business Analyst will pre pare the FRS.
Based on this we are going to prepare test cases.
It contains
1. Over view of the project
2. Page elements of the Application (Filed Names)
3. Prototype of the of the application
4. Business rules and Error States
5. Data Flow diagrams
6. Use cases contains Actor and Actions and System Responses
16. How you can decide the number of
test cases is enough for testing the given module?
The developed test cases are covered
all the functionality of the application we can say test cases are enough. If u
knows the functionality covered or not u can use RTM.
17. What is the difference between
Retesting and Data Driven Testing?
Retesting: it is manual process in
which application will be tested with entire new set of data.
Data Driven Testing(DDT)-It is a Automated testing process in which application is tested with multiple test dated is very easy procedure than retesting because the tester should sit and need to give different new inputs manually from front end and it is very tedious and boring
Procedure.
Data Driven Testing(DDT)-It is a Automated testing process in which application is tested with multiple test dated is very easy procedure than retesting because the tester should sit and need to give different new inputs manually from front end and it is very tedious and boring
Procedure.
18. What is regression testing?
After the Bug fixed, testing the
application whether the fixed bug is affecting remaining functionality of the
application or not.Majorly in regression testing Bug fixed module and it’s
Connected modules are checked for their integrity after bug fixation.
Connected modules are checked for their integrity after bug fixation.
19. How does u test web application?
Web application testing
Web application should have the following features like
1. Attractive User Interface (logos, fonts, alignment)
2. High Usability options
3. Security features (if it has login feature)
4. Database (back end).
5. Performance (appearing speed of the application on client system)
6. Able to work on different Browsers (Browser compatibility), O.S compatibility (technically called as portability)
7. Broken link testing………etc
so we need to follow out the following test strategy.
1. Functionality Testing
2. Performance Testing (Load, volume, Stress, Scalability)
3. Usability Testing
4. User Interface Testing (colors, fonts, alignments…)
5. Security Testing
6. Browser compatibility Testing (different versions and different browser)
7. Broken link and Navigation Testing
8. Database (back end) Testing (data integrity)
9. Portability testing (Multi O.s Support)….etc
Web application should have the following features like
1. Attractive User Interface (logos, fonts, alignment)
2. High Usability options
3. Security features (if it has login feature)
4. Database (back end).
5. Performance (appearing speed of the application on client system)
6. Able to work on different Browsers (Browser compatibility), O.S compatibility (technically called as portability)
7. Broken link testing………etc
so we need to follow out the following test strategy.
1. Functionality Testing
2. Performance Testing (Load, volume, Stress, Scalability)
3. Usability Testing
4. User Interface Testing (colors, fonts, alignments…)
5. Security Testing
6. Browser compatibility Testing (different versions and different browser)
7. Broken link and Navigation Testing
8. Database (back end) Testing (data integrity)
9. Portability testing (Multi O.s Support)….etc
20. How does u perform regression
testing, means what test cases u select for regression?
Regression testing will be conducted
after any bug fixed or any functionality changed.
During defect fixing procedure some part of coding may be changed or functionality may be manipulated. In this case the old test cases will be updated or completely re written
According to new features of the application where bug fixed area. Here possible areas are old test cases will be executed as usual or some new test cases will be added to existing test cases or some test cases may be deleted.
During defect fixing procedure some part of coding may be changed or functionality may be manipulated. In this case the old test cases will be updated or completely re written
According to new features of the application where bug fixed area. Here possible areas are old test cases will be executed as usual or some new test cases will be added to existing test cases or some test cases may be deleted.
21. What r the client side scripting
languages and server side scripting languages?
Client side scripting languages are
Javascript, VbScript, PHP…etc
Server side Scripting languages are
Perl, JSP, ASP, PHP.etc
Client side scripting languages are useful to validate the inputs or user actions from user side or client side.
Server side Scripting languages are to validate the inputs at server side.
These scripting languages provide security for the application. And also provides dynamic nature to web or client server application
Client side scripting is good because it won’t send the unwanted input’s to server for validation. From front-end it self it validated the user inputs and restricts the user activities and guides him
Javascript, VbScript, PHP…etc
Server side Scripting languages are
Perl, JSP, ASP, PHP.etc
Client side scripting languages are useful to validate the inputs or user actions from user side or client side.
Server side Scripting languages are to validate the inputs at server side.
These scripting languages provide security for the application. And also provides dynamic nature to web or client server application
Client side scripting is good because it won’t send the unwanted input’s to server for validation. From front-end it self it validated the user inputs and restricts the user activities and guides him
22. If a very low defect (user
interface) is detected by u and the developer not compromising with that
defect,what will u do?
User interface defect is a high visibility defect and easy to reproduce.
Follow the below procedure
1. Reproduce the defect
2. Capture the defect screen shots
3. Document the proper inputs that you are used to get the defect in the defect report
3. Send the defect report with screen shots, i/ps and procedure for defect reproduction.
Before going to this you must check your computer hard ware configuration that is same as developer system configuration. And also check the system graphic drivers are properly
Installed or not. If the problem in graphic drivers the User interfaces error will come.
So first check your side if it is correct from your side then reports the defect by following the above method.
User interface defect is a high visibility defect and easy to reproduce.
Follow the below procedure
1. Reproduce the defect
2. Capture the defect screen shots
3. Document the proper inputs that you are used to get the defect in the defect report
3. Send the defect report with screen shots, i/ps and procedure for defect reproduction.
Before going to this you must check your computer hard ware configuration that is same as developer system configuration. And also check the system graphic drivers are properly
Installed or not. If the problem in graphic drivers the User interfaces error will come.
So first check your side if it is correct from your side then reports the defect by following the above method.
23.if u r only person in the office
and client asked u for some changes and u didn’t get what the client asked for
what will u do?
One thing here is very important. Nobody will ask test engineer to change software that is
not your duty, even if it is related to testing and anybody is not there try to listen care fully if you are not understand ask him again and inform to the corresponding people immediately.
Here the client need speedy service, we (our company) should not get any blame from customer side.
One thing here is very important. Nobody will ask test engineer to change software that is
not your duty, even if it is related to testing and anybody is not there try to listen care fully if you are not understand ask him again and inform to the corresponding people immediately.
Here the client need speedy service, we (our company) should not get any blame from customer side.
24. How to get top two salaries from
employee tables?
Select * from EMP e where 2>= (select count (*) from EMP e where sal>e.sal) order by desc sal.
Select * from EMP e where 2>= (select count (*) from EMP e where sal>e.sal) order by desc sal.
25. How many Test-Cases can be written
for the calculator having 0-9 buttons, Add, Equalto buttons? The test cases
should be focused only on add-functionality but mot GUI.What is those
test-cases?
Test-Cases for the calculator
so here we have 12 buttons totalize 0,1,2,3,4,5,6,7,8,9,ADD,Equalto -12 buttons
here u can press at least 4 buttons at a time minimum for example 0+1= for zero u should press ‘zero’ labeled button for plus u should press ‘+’ labeled button for one u should press ‘one’ labeled button for equal to u should press ‘equal to’ labeled button 0+1=here + and = positions will not vary so first number position can be varied from 0 to 9 i.e. from permutation and combinations u can fill that space in 10 ways in the same way second number position can be varied from 0 to 9 i.e. from permutation and combinations u can fill that space in 10 ways
Total number of possibilities are =10×10=100
This is exhaustive testing methodology and this is not possible in all cases.
In mathematics we have one policy that the function satisfies the starting and ending values of a range then it can satisfy for entire range of values from starting to ending.
then we check the starting conditions i.e. one test case for ‘0+0=’ (expected values you know that’s ‘0′) then another test case for ‘9+9=’(expected values you know that’s ‘18′) only two test cases are enough to test the calculator functionality.
Test-Cases for the calculator
so here we have 12 buttons totalize 0,1,2,3,4,5,6,7,8,9,ADD,Equalto -12 buttons
here u can press at least 4 buttons at a time minimum for example 0+1= for zero u should press ‘zero’ labeled button for plus u should press ‘+’ labeled button for one u should press ‘one’ labeled button for equal to u should press ‘equal to’ labeled button 0+1=here + and = positions will not vary so first number position can be varied from 0 to 9 i.e. from permutation and combinations u can fill that space in 10 ways in the same way second number position can be varied from 0 to 9 i.e. from permutation and combinations u can fill that space in 10 ways
Total number of possibilities are =10×10=100
This is exhaustive testing methodology and this is not possible in all cases.
In mathematics we have one policy that the function satisfies the starting and ending values of a range then it can satisfy for entire range of values from starting to ending.
then we check the starting conditions i.e. one test case for ‘0+0=’ (expected values you know that’s ‘0′) then another test case for ‘9+9=’(expected values you know that’s ‘18′) only two test cases are enough to test the calculator functionality.
26. What is positive and negative
testing. Explain with example?
Positive Testing - testing the system by giving the valid data.
Negative Testing - testing the system by giving the Invalid data.
For Exam application contains a textbox and as per the user’s Requirements the textbox should accept only Strings. By providing only String as input data to the textbox & to check whether its working properly or not means it is Positive Testing. If giving the input other than String means it is negative Testing.
Positive Testing - testing the system by giving the valid data.
Negative Testing - testing the system by giving the Invalid data.
For Exam application contains a textbox and as per the user’s Requirements the textbox should accept only Strings. By providing only String as input data to the textbox & to check whether its working properly or not means it is Positive Testing. If giving the input other than String means it is negative Testing.
27. How will you prepare Test plan.
What are the techniques involved in preparing the Test plan?
Test plan means planning for the release. This includes Project background
Test Objectives: Brief overview and description of the document
Test Scope: setting the boundaries
Features being tested (Functionalities)
Hardware requirements
Software requirements
Entrance Criteria (When to start testing):
Test environment established, Builder received from developer, Test case prepared and reviewed.
Exit criteria (when to stop testing):
All bug status cycle are closed, all functionalities are tested, and all high and medium bugs are resolved.
Project milestones: dead lines
Test plan means planning for the release. This includes Project background
Test Objectives: Brief overview and description of the document
Test Scope: setting the boundaries
Features being tested (Functionalities)
Hardware requirements
Software requirements
Entrance Criteria (When to start testing):
Test environment established, Builder received from developer, Test case prepared and reviewed.
Exit criteria (when to stop testing):
All bug status cycle are closed, all functionalities are tested, and all high and medium bugs are resolved.
Project milestones: dead lines
28. What is the Defect Life Cycle?
Defect life cycle is also called as bug life cycle. It has 6stages namely
1. New: found new bug
2. Assigned: bud assigned to developer
3. Open: developer is fixing the bug
4. Fixed: developer has fixed the bug
5. Retest: tester retests the application
6. closed/reopened: if it is ok tester gives closed statuselse he reopens and sends back to developer.
Defect life cycle is also called as bug life cycle. It has 6stages namely
1. New: found new bug
2. Assigned: bud assigned to developer
3. Open: developer is fixing the bug
4. Fixed: developer has fixed the bug
5. Retest: tester retests the application
6. closed/reopened: if it is ok tester gives closed statuselse he reopens and sends back to developer.
29. Expalin about metrics Management?
Metrics: is nothing but a measurement analysis.Measurment analysis and Improvement is one of the process area in CMM I L2.
Metrics: is nothing but a measurement analysis.Measurment analysis and Improvement is one of the process area in CMM I L2.
30. What is performance Testing and
Regression Testing?
Performance Testing:-testing the present working condition of the product
Regression Testing:-Regression Testing is checking for the newly added functionality causing any errors interims of functionality and the common functionality should be stable
In the latest and the previous versions
Performance Testing:-testing the present working condition of the product
Regression Testing:-Regression Testing is checking for the newly added functionality causing any errors interims of functionality and the common functionality should be stable
In the latest and the previous versions
31.How do you review test case? Type
of Review…
Types of reviewing test cases depend upon company standards, viz..,
Peer review, team lead review, project manager review.
Some times client may also review the test cases reg what is approach following for project
Types of reviewing test cases depend upon company standards, viz..,
Peer review, team lead review, project manager review.
Some times client may also review the test cases reg what is approach following for project
32. In which way tester get
Build A, Build B, Build Z of an application, just explains the process?
After preparation of test cases project manager will release software release note in that Document there will be URL path of the website link from that we will receive
The build In case of web server projects, you will be provided with an URL or a 92.168. ***. *** (Web address) which will help you access the project using a browser from your system.
After preparation of test cases project manager will release software release note in that Document there will be URL path of the website link from that we will receive
The build In case of web server projects, you will be provided with an URL or a 92.168. ***. *** (Web address) which will help you access the project using a browser from your system.
In case of Client server, the build
is placed in the VSS (Configuration tool) which will help you
get the .exe downloaded to your computer.
33. Apart from bug reporting what is
your involvement in project life cycle?
As a Test engineer we design test cases, prepare test cases Execute Test cases, track the bugs, analyze the results report the bugs. Involved in regression testing, performance of system
Testing system integration testing at last preparation of Test summary Report
As a Test engineer we design test cases, prepare test cases Execute Test cases, track the bugs, analyze the results report the bugs. Involved in regression testing, performance of system
Testing system integration testing at last preparation of Test summary Report
34.What are the contents of test report?
There are two documents, which should be prepared at particular phase.
1. Test Results document.
2. Test Report document.
Test Results doc will be prepared at the phase of each type of Testing like FULL FUNCTIONAL TEST PASS,REGRESSION TEST PASS,SANITY TEST PASS etc…Test case execution against
The application. Once you prepared this doc, we will send the doc to our TL and PM.By seeing the Test Results doc, TL will come to know the coverage part of the testcase.Here I am giving you the contents used in the Test Results doc?
1. Build No
2. Version Name
3. Client OS
4. Feature set
5. Main Feature
6. Defined Test cases on each feature.
7. QA engineer Name
8. Test e-cases executed. (Includes pass and fail)
9. Testcases on HOLD (Includes blocking test cases and deferred Test cases)
10. Covereage Report (Which includes the coverage ratings in %, like % of test cases covered, % of test cases failed)
Coming to Test report, generally we will prepare Test report, once we rolled out the product to our client. This document will be prepared by TL and delivered to the client.Mainly, this document describes the what we have done in the project, chievements we have reached, our
Learning’s in throughout the project etc…The other name for Test report is Project Closure Report and we will summarize the all the activities, which have taken place in through out the project. Here I am giving your the contents covered in the Test Report.
1. Test Environment (Should be covered the OS, Application or webservers, Mahchine names, Database, etc…)
2.Test Methods(Types of Tests, we have done in the project like Functional Testing, Platform Testing, regression Testing,etc..
3. Major areas Covered.
4. Bug Tracking Details. (Includes inflow and outflow of the bus in our delivered project)
5. Work schedule (When we start the testing and we finished)
6. Defect Analysis
6.1 Defects logged in different types of tests like Functional Test, regressiion Test as per area wised.
6.2 State of the Defects at end of the Test cycle.
6.3 Root cause analysis for the bugs marked as NOT A BUG.
7. QA observations or learning’s thought the life cycle.
35. Write high level test cases?
Write all the test cases under high level TC, which can be covered the main functionalities like
Creation, edition, deletion, etc….as per prescribed in the screen.
Write all the test cases under low level TC,which can be covered the screen, like input fields are displayed as per the requirements, buttons are enabled or disabled, and test case for low priority functionalities.
Example a screen contains two edit boxes login and password and a put buttons OK and Reset and check box for the label “Remember my password”. Now let us write high level TC
And low level test cases.
Write all the test cases under high level TC, which can be covered the main functionalities like
Creation, edition, deletion, etc….as per prescribed in the screen.
Write all the test cases under low level TC,which can be covered the screen, like input fields are displayed as per the requirements, buttons are enabled or disabled, and test case for low priority functionalities.
Example a screen contains two edit boxes login and password and a put buttons OK and Reset and check box for the label “Remember my password”. Now let us write high level TC
And low level test cases.
HIGH LEVEL TC
1. Verify that User is able to login with valid login and valid password.
2. Verify that User is not able to login with invalid login and valid password.
Etc…
..
3. Verify that Reset button clears the filled screen.
4. Verify that a pop up message is displayed for blank login.
Etc…
Etc.
1. Verify that User is able to login with valid login and valid password.
2. Verify that User is not able to login with invalid login and valid password.
Etc…
..
3. Verify that Reset button clears the filled screen.
4. Verify that a pop up message is displayed for blank login.
Etc…
Etc.
LOW LEVEL TC
1. Verify that after launching the URL of the application below fields are displays in the screen.
1. Login Name 2.Password.3.OK BUTTON 4.RESET button etc.
5. Check box, provided for the label “remember my pwd” is unchecked.
2. Verify that OK button should be disabled before selecting login and password fields.
3. Verify that OK button should we enabled after selecting login and password.
4. Verify that User is able to check the check box, providedfor the label “remember my password”.
Etc.
In this way, we can categories all the test cases under HIGH LEVEL and LOW LEVEL.
1. Verify that after launching the URL of the application below fields are displays in the screen.
1. Login Name 2.Password.3.OK BUTTON 4.RESET button etc.
5. Check box, provided for the label “remember my pwd” is unchecked.
2. Verify that OK button should be disabled before selecting login and password fields.
3. Verify that OK button should we enabled after selecting login and password.
4. Verify that User is able to check the check box, providedfor the label “remember my password”.
Etc.
In this way, we can categories all the test cases under HIGH LEVEL and LOW LEVEL.
36. What is test scenario?
Test scenario will be framed on basis of the requirement, which need to be checked. For that, we will frame set of test cases, in other terms, we can say all the conditions, which can be determined the testing coverage against business requirement.
Please see the below example, which is exactly matched to my explanation.
As we know all most all the application are having login screen, which contains login name and password. Here is the test scenario for login screen.
Scenario: USER’S LOGIN
Conditions to be checked to test the above scenario:
—————————————————-
1. Test login field and Password fields individually.
2. Try to login with valid login and valid password.
3. Try to login with invalid login and valid password. Etc
Test scenario will be framed on basis of the requirement, which need to be checked. For that, we will frame set of test cases, in other terms, we can say all the conditions, which can be determined the testing coverage against business requirement.
Please see the below example, which is exactly matched to my explanation.
As we know all most all the application are having login screen, which contains login name and password. Here is the test scenario for login screen.
Scenario: USER’S LOGIN
Conditions to be checked to test the above scenario:
—————————————————-
1. Test login field and Password fields individually.
2. Try to login with valid login and valid password.
3. Try to login with invalid login and valid password. Etc
37. What is build duration?
it is a tine gap between old version build and new version build in new version build some new extra features are added
it is a tine gap between old version build and new version build in new version build some new extra features are added
38. What is test deliverables?
Test deliverables are nothing but documents preparing after testing like test plan document test case template bug report template Test deliverables will be delivered to the client not only for the completed activities, but also for the activites, which we are implementing for the better productivity. (As per the company’s standards).Here I am giving you some of the Test deliverables in my project.
1. QA Test Plan
2. Test case Docs
3. QA Test plan, if we are using Automation.
4. Automation scripts
5. QA Coverage Matrix and defect matrix.
6. Traceability Matrix
7. Test Results doc
8. QA Schedule doc (describes the deadlines)
9. Test Report or Project Closure Report. (Prepared once we rolled out the project to client)
10. Weekly status report (sent by PM to the client)
11. Release Notes.
Test deliverables are nothing but documents preparing after testing like test plan document test case template bug report template Test deliverables will be delivered to the client not only for the completed activities, but also for the activites, which we are implementing for the better productivity. (As per the company’s standards).Here I am giving you some of the Test deliverables in my project.
1. QA Test Plan
2. Test case Docs
3. QA Test plan, if we are using Automation.
4. Automation scripts
5. QA Coverage Matrix and defect matrix.
6. Traceability Matrix
7. Test Results doc
8. QA Schedule doc (describes the deadlines)
9. Test Report or Project Closure Report. (Prepared once we rolled out the project to client)
10. Weekly status report (sent by PM to the client)
11. Release Notes.
39. What is your involvement in test
plan?
Test lead is involved in preparing
test plan test engineers are no way related in preparing test plan role TE is
test case design, and execution and bug tracking and reporting them Generally
TL is involved in preparation of the TestPlan.But it is not mandatory only TL
will take main part in the preparation of the TP.Test engineer can suggest to
TL, if he (or) she has good understanding on project and resources, if he or
she has more exp with the project, if TL is wrongly given deadlines. If your
suggestions are valid, TL will incorporate all of them to the TestPlan.But in
most of the companies Test engineers are just audience.
40. Which test cases are not to be
automated?
All the test cases which are related to a feature of the product, that keeps on changing (there are always some or the other enhancements in it). Frequent enhancements may change the UI, add/remove few controls. Hence such cases, if automated, would involve lot of a intendance
All the test cases which are related to a feature of the product, that keeps on changing (there are always some or the other enhancements in it). Frequent enhancements may change the UI, add/remove few controls. Hence such cases, if automated, would involve lot of a intendance
41. If a project is long term
project, requirements are also changes then test plan will change or not? Why?
Yes. Definitely. If requirement changes, the design documents, specifications (for that particular module which implements the requirements) will also change. Hence the test plan would also need to be updated. This is because “Resource Allocation” is one section in the test
Plan. We would need to write new test cases, review, and execute it. Hence resource allocation would have to be done accordingly. As a result the Test plan would change
Yes. Definitely. If requirement changes, the design documents, specifications (for that particular module which implements the requirements) will also change. Hence the test plan would also need to be updated. This is because “Resource Allocation” is one section in the test
Plan. We would need to write new test cases, review, and execute it. Hence resource allocation would have to be done accordingly. As a result the Test plan would change
42. Explain VSS (Virtual Source
Safe)?
After completion of all phages from development side developer store the code in development folder of VSS, Testing team copying code from that folder to testing folder, after completing above phages from testing, testers put the build in base line folder. It is version control Tool
Mainly useful to developer, to storing code and maintains version Copying a code from VSS By developer is called CHECK-IN Upload the code in to VSS is called CHECK-OUT.
After completion of all phages from development side developer store the code in development folder of VSS, Testing team copying code from that folder to testing folder, after completing above phages from testing, testers put the build in base line folder. It is version control Tool
Mainly useful to developer, to storing code and maintains version Copying a code from VSS By developer is called CHECK-IN Upload the code in to VSS is called CHECK-OUT.
43. Who will assign severity &
priority?
The tester/developer should give the priority based on severity of the bug
Severity means: is the impact of the bug on the application .i.e seriousness of the bug interims of the functionality.
Priority means: is how soon it should get fixed i.e. importance of the bug interims of customer
The tester/developer should give the priority based on severity of the bug
Severity means: is the impact of the bug on the application .i.e seriousness of the bug interims of the functionality.
Priority means: is how soon it should get fixed i.e. importance of the bug interims of customer
44. What is the Difference between
Stub Testing and Driver Testing?
Stub testing:
In top down approach, a core module is developed. To test that core module, small dummy modules r used. So stubs r small dummy modules that test the core module.
Driver testing:
In bottom up approach, small modules r developed. To test them a dummy core module called driver is developed.
Stub testing:
In top down approach, a core module is developed. To test that core module, small dummy modules r used. So stubs r small dummy modules that test the core module.
Driver testing:
In bottom up approach, small modules r developed. To test them a dummy core module called driver is developed.
45. What is a “Good Tester”?
Is one who tries to break the developers software and in a position to venture the bugs. So that at least 80% bugs free software can deliver.
Is one who tries to break the developers software and in a position to venture the bugs. So that at least 80% bugs free software can deliver.
46. What is cookie And Session
testing?
A small text file of information that certain Web sites attach to a user’s hard drive while the user is browsing the Web site. A Cookie can contain information such as user ID, user preferences, archive shopping cart information, etc. Cookies can contain Personally Identifiable
Information. Session is a connection between a server and client.
A small text file of information that certain Web sites attach to a user’s hard drive while the user is browsing the Web site. A Cookie can contain information such as user ID, user preferences, archive shopping cart information, etc. Cookies can contain Personally Identifiable
Information. Session is a connection between a server and client.
47. How would you perform testing
manually for web site?
By noting the time to load page or perform any action with stop watch. I know it sounds funny but this is the way performance is tested manualy.
By noting the time to load page or perform any action with stop watch. I know it sounds funny but this is the way performance is tested manualy.
48. What is use case? Tell me the
attribute of use case?
“Use Case is description of functionality certain features of an application interims of Actors, actions and responsibilities.”
Use Case attributes are:
1. Information of Document, 2. Description, 3. Objective, 4. Actors, 5.Pre-conditions, 6.Data-element descriptions, 7.post conditions, 8.primary flow, 9. Alternative flow and Business rules/interaction implementations and etc….
“Use Case is description of functionality certain features of an application interims of Actors, actions and responsibilities.”
Use Case attributes are:
1. Information of Document, 2. Description, 3. Objective, 4. Actors, 5.Pre-conditions, 6.Data-element descriptions, 7.post conditions, 8.primary flow, 9. Alternative flow and Business rules/interaction implementations and etc….
49. What is the difference between
stress, volume and load testing?
Load Testing gradually increase the load and check the performance of the application .v check at what point or maximum load application can sustain.
Stress testing: In this testing v check the performance of application under extreme condign which rarely occurs like
(1)Many concurrent user access the application for short time.
(2) Extra ordinary long transaction.
(3) Very short transaction reputed quickly.
Load Testing gradually increase the load and check the performance of the application .v check at what point or maximum load application can sustain.
Stress testing: In this testing v check the performance of application under extreme condign which rarely occurs like
(1)Many concurrent user access the application for short time.
(2) Extra ordinary long transaction.
(3) Very short transaction reputed quickly.
50. When will you do the beta test?
When will you do the alpha test?
Alpha and Beta tests comes under User acceptance test. We will conduct these two systems being released. We are giving opportunity to customer to check all punctualities covered or not.
Alpha testing conducting for software application by real customer at development site.
Beta testing conducting for software product by model customer at customer site.
Alpha and Beta tests comes under User acceptance test. We will conduct these two systems being released. We are giving opportunity to customer to check all punctualities covered or not.
Alpha testing conducting for software application by real customer at development site.
Beta testing conducting for software product by model customer at customer site.
52. How do you select test cases for
Regression Testing (The point is when there is change code how do you come to
know which part of code or modules it will affect)?
Consider an example of a form which has a user name, password and Login button.
There is a code change and a new button “Reset” is introduced. Regression testing (for that build) will include testing only the “Login” button and not the Reset button (testing Reset button will be a part of conation testing). Hence the Regression tester need not worry about the change in code, functionality. But he has to make sure that the existing functionality is working as desired. Testing of “Reset” button will be included as a part of Regression, for the next build
Consider an example of a form which has a user name, password and Login button.
There is a code change and a new button “Reset” is introduced. Regression testing (for that build) will include testing only the “Login” button and not the Reset button (testing Reset button will be a part of conation testing). Hence the Regression tester need not worry about the change in code, functionality. But he has to make sure that the existing functionality is working as desired. Testing of “Reset” button will be included as a part of Regression, for the next build
53. Can you explain with example of
high seviority and low priority, low seviority and high priority, high
seviority and high priority, low seviority and low priority?
1. High severity and high priority - Database connectivity cannot be established by multiple users.
2. Low severity and low priority - Small issues like, incorrect number of decimal digits in the output.
3. Low severity and high priority - Images not updated.
4. High severity and low priority - In a module of say 2 interfaces, the link between them is broken or is not functioning.
(1)High priority & High Severity: If u clicks on explorer icon or any other icon then system crash.
(2) Low priority & low severity: In login window, spell of ok button is “Ko”.
(3)Low priority & high serverty: In login window, there is a restriction login name should be 8 characters if user enter 9 or than 9 in that case system get crash.
(4)High priority & low severity: Suppose logo of any brand company is not proper in their product. So it affects their business.
1. High severity and high priority - Database connectivity cannot be established by multiple users.
2. Low severity and low priority - Small issues like, incorrect number of decimal digits in the output.
3. Low severity and high priority - Images not updated.
4. High severity and low priority - In a module of say 2 interfaces, the link between them is broken or is not functioning.
(1)High priority & High Severity: If u clicks on explorer icon or any other icon then system crash.
(2) Low priority & low severity: In login window, spell of ok button is “Ko”.
(3)Low priority & high serverty: In login window, there is a restriction login name should be 8 characters if user enter 9 or than 9 in that case system get crash.
(4)High priority & low severity: Suppose logo of any brand company is not proper in their product. So it affects their business.
54. What will be the Test case for
ATM Machine & Coffee Machine?
Test cases for ATM Machine
1. Successful inspection of ATM card
2. Un successful operation due to insert card in wrong angle
3. Un successful operation due to invalid account ex: other bank card or time expired card
4. Successful entry of PIN number
5. Un successful operation due to enter wrong PIN number 3times
6. Successful selection of language
Test cases for ATM Machine
1. Successful inspection of ATM card
2. Un successful operation due to insert card in wrong angle
3. Un successful operation due to invalid account ex: other bank card or time expired card
4. Successful entry of PIN number
5. Un successful operation due to enter wrong PIN number 3times
6. Successful selection of language
7. Successful selection of account
type
8. Un successful operation due to invalid account type
10. Successful selection of withdraw operation
11. Successful selection of amount to be withdraw
12. Successful withdraw operation
13. Unsuccessful withdraw operation due to wrong denominations
14. Unsuccessful withdraw operation due to amount is greater than day limit
15. Unsuccessful withdraw operation due to lack of money in ATM
16. Unsuccessful withdraw operation due to amount is greater than possible balance
17. Unsuccessful withdraw operation due to transactions is greater than day limit
18. Unsuccessful withdraw operation due to click cancel after insert card
19. Unsuccessful withdraw operation due to click cancel after insert card & pin number
20. Unsuccessful withdraw operation due to click cancel after insert card, pin number & language
21. Unsuccessful withdraw operation due to click cancel after insert card, pin number, language &account type
22. Unsuccessful withdraw operation due to click cancel after insert card , pin number , language ,account type & withdraw operation
23.unsuccessful withdraw operation due to click cancel after insert card , pin number , language ,account type ,withdraw operation &amount to be withdraw
8. Un successful operation due to invalid account type
10. Successful selection of withdraw operation
11. Successful selection of amount to be withdraw
12. Successful withdraw operation
13. Unsuccessful withdraw operation due to wrong denominations
14. Unsuccessful withdraw operation due to amount is greater than day limit
15. Unsuccessful withdraw operation due to lack of money in ATM
16. Unsuccessful withdraw operation due to amount is greater than possible balance
17. Unsuccessful withdraw operation due to transactions is greater than day limit
18. Unsuccessful withdraw operation due to click cancel after insert card
19. Unsuccessful withdraw operation due to click cancel after insert card & pin number
20. Unsuccessful withdraw operation due to click cancel after insert card, pin number & language
21. Unsuccessful withdraw operation due to click cancel after insert card, pin number, language &account type
22. Unsuccessful withdraw operation due to click cancel after insert card , pin number , language ,account type & withdraw operation
23.unsuccessful withdraw operation due to click cancel after insert card , pin number , language ,account type ,withdraw operation &amount to be withdraw
55. Tell me about your daily
activities as a test engineer?
Role:
1. Understanding the BRS and Use cases Document
2. Giving system demo to PM, System analyst, designer, Dev lead.
3. Preparing the Test Actions in xls sheet.
4. Updating the Test Actions based on review comments by System analyst/Business Analyst.
5. Preparing the Test cases and Datasets (System level and global level datasets) in word document
6. Updating the Test Cases based on review comments by System analyst.
7. Installing the application-Testing environment set up.
8. Performing Functional, GUI, System, Compatibility testing (If necessary), Regression testing based on Test cases
9. Preparing the defect report, Bug tracking list and sending daily status report to PM, leads.
Role:
1. Understanding the BRS and Use cases Document
2. Giving system demo to PM, System analyst, designer, Dev lead.
3. Preparing the Test Actions in xls sheet.
4. Updating the Test Actions based on review comments by System analyst/Business Analyst.
5. Preparing the Test cases and Datasets (System level and global level datasets) in word document
6. Updating the Test Cases based on review comments by System analyst.
7. Installing the application-Testing environment set up.
8. Performing Functional, GUI, System, Compatibility testing (If necessary), Regression testing based on Test cases
9. Preparing the defect report, Bug tracking list and sending daily status report to PM, leads.
56. In SDLC process what is the role
of PM, TL, DEVELOPER, tester in each and every phase? Please explain me in
detail?
In the SDLC we have these phases
1. Initial phase
2. Analysis phase
3. Designing phase
4. Coding phase
5. Testing
6. Delivery and maintenance
In the SDLC we have these phases
1. Initial phase
2. Analysis phase
3. Designing phase
4. Coding phase
5. Testing
6. Delivery and maintenance
In the initial phase project manager
can prepare a document for the requirements, team leader will prepare a team
which is having test engineers, developer will provided by the project manager,
tested will prepare test cases for that particular project
Analysis phase all the members have a meeting to finalize the technology to develop that project, the employee, time…
Designing phase the project manager like senior level management will give the directions and source code to the team members to develop the actual code that is guidelines will be given in this phase
Coding phase developer will develop the actual code using the source code and they release the application to the tested
Testing phase they deploy their test cases to that application and prepare a bug profile document if there is any defect/bug in that application and send it back to developer, developer may rectify and releases than application as next build and if the bug not understand it will send to the project lead in the delivery phase the so test eng can deploy the application in the client environment
Maintenance phase if the client get any problem with the application it may solved by the project lead with help of testers and developers
57. How do you Test Application with having any requirement and Document?
If it is an existing system or if a build is available then we explore the system while testing. This helps knowing the functional use of the system, and its usability.
By asking questions to end users and how they use it will be more beneficial. Also, you may work with BA to know more about the system.
Black box test is nothing but the same where you explore the system without having any prior knowledge to the system.
Analysis phase all the members have a meeting to finalize the technology to develop that project, the employee, time…
Designing phase the project manager like senior level management will give the directions and source code to the team members to develop the actual code that is guidelines will be given in this phase
Coding phase developer will develop the actual code using the source code and they release the application to the tested
Testing phase they deploy their test cases to that application and prepare a bug profile document if there is any defect/bug in that application and send it back to developer, developer may rectify and releases than application as next build and if the bug not understand it will send to the project lead in the delivery phase the so test eng can deploy the application in the client environment
Maintenance phase if the client get any problem with the application it may solved by the project lead with help of testers and developers
57. How do you Test Application with having any requirement and Document?
If it is an existing system or if a build is available then we explore the system while testing. This helps knowing the functional use of the system, and its usability.
By asking questions to end users and how they use it will be more beneficial. Also, you may work with BA to know more about the system.
Black box test is nothing but the same where you explore the system without having any prior knowledge to the system.
58. What is back end testing using
SQL?
Executing SQL statements to check if the data submitted by a GUI program is updated in the database or not? Executing the statement the data base is connecting to that particular changes, updations or not it will test. Back end testing is the testing the integration between the application and the database. It is checking the changes made in the database are getting reflected in the application.
Example: A new column is added in the table. Here we test by giving values in the application and value has to be stored in the table.
Executing SQL statements to check if the data submitted by a GUI program is updated in the database or not? Executing the statement the data base is connecting to that particular changes, updations or not it will test. Back end testing is the testing the integration between the application and the database. It is checking the changes made in the database are getting reflected in the application.
Example: A new column is added in the table. Here we test by giving values in the application and value has to be stored in the table.
59. What are the reasons why
parameterization is necessary when load testing the Web server and the database
server?
When you test your applications, you may want to check how the application performs the same operations with multiple sets of data. For example, suppose you want to check how
Your Web site responds to ten separate sets of data. You could record ten separate tests, each with its own set of data. Alternatively, you can create Data Table parameters so that your test runs ten times, each time using a different set of data.
When you test your applications, you may want to check how the application performs the same operations with multiple sets of data. For example, suppose you want to check how
Your Web site responds to ten separate sets of data. You could record ten separate tests, each with its own set of data. Alternatively, you can create Data Table parameters so that your test runs ten times, each time using a different set of data.
60. Difference between strategic test
plan & test plan?
Strategic test is an organizational level term which is applied for all the projects in the organization with small customizations
Test plan is project level term and which can be applied for that specific project only.
Test plan is a strategic document which describes how to perform testing in an efficient effective and uptimes way. Quality lead test lead can prepare this test plan
Strategic test plan is an already or new test plan which can bow used in the future for another project also with some changes in the same organisation.
Strategic test is an organizational level term which is applied for all the projects in the organization with small customizations
Test plan is project level term and which can be applied for that specific project only.
Test plan is a strategic document which describes how to perform testing in an efficient effective and uptimes way. Quality lead test lead can prepare this test plan
Strategic test plan is an already or new test plan which can bow used in the future for another project also with some changes in the same organisation.
61. Draw Backs of automated testing?
DRAW BACKS OF AUTMATION
Expensive, lack of expertisation, all the areas we can not automate
DRAW BACKS OF AUTMATION
Expensive, lack of expertisation, all the areas we can not automate
62. When will u make update and
modify the test object properties in the repository?
When ever the developer may change any one of the object properties definitely we have to change the same in the OR object repository. If new version net build released from the development department we the test engineers must to modify or update the same is compulsory, other wise than test will show the bug
When ever the developer may change any one of the object properties definitely we have to change the same in the OR object repository. If new version net build released from the development department we the test engineers must to modify or update the same is compulsory, other wise than test will show the bug
63. What is the document needed to
create a test case? How u tell it is test case?
System requirements specification, Use case document, Test Plan
System requirements specification, Use case document, Test Plan
64. In customer details form having
fields like customer name, customer address. After completion of this module,
client raise the change as insert the two radio buttons after customer address.
How you can check as a tester?
1. First we need to verify whether the radio button is there are not?
2. Conform the radio buttons are present after the customer address or not.
3. Verify the no of radio button.
4. Verify only one radio button should be checked initially when we open the Customer details form (if it is mentioned in FS)
5. Verify the functionality of the radio buttons i.e. if we check one ratio button, second radio button should be unchecked.
6. Verify the spell check of radio button label name.
7. Verify the alignment of radio buttons in the form.
1. First we need to verify whether the radio button is there are not?
2. Conform the radio buttons are present after the customer address or not.
3. Verify the no of radio button.
4. Verify only one radio button should be checked initially when we open the Customer details form (if it is mentioned in FS)
5. Verify the functionality of the radio buttons i.e. if we check one ratio button, second radio button should be unchecked.
6. Verify the spell check of radio button label name.
7. Verify the alignment of radio buttons in the form.
65. At the time of testing web based applications and client server applications, what you absorbed as a tester?
We generally check for the links, data retrieving and posting.
We perform load and stress testing especially for Web based and Client-Server applications.
66. What are the documents required
to prepare test plan?
Introduction, scope, test team and their responsibilities, test environment S/W & H/W requirements, test data preparation, levels of testing, seviority & priority, schedule, risk, automation Plan, features to test, bug life cycle all these are documents of test plan.
Introduction, scope, test team and their responsibilities, test environment S/W & H/W requirements, test data preparation, levels of testing, seviority & priority, schedule, risk, automation Plan, features to test, bug life cycle all these are documents of test plan.
67. What is testing policy and
testing methodology? And what is the difference?
Testing policy means all types of testing or testing techniques (i.e. functional testing, sanity testing etc).Testing methodology means white box and black box testing.
68. What is comparison testing?
Comparison Testing means comparing your software with the better one or you’re Competitor.
While comparison Testing we basically compare the Performance of the software. For ex If you have to do Comparison Testing of PDF converter(Desktop Based Application) then you will compare your software with your Competitor on the basis of:-
1. Speed of Conversion PDF file into Word.
2. Quality of converted file.
Testing policy means all types of testing or testing techniques (i.e. functional testing, sanity testing etc).Testing methodology means white box and black box testing.
68. What is comparison testing?
Comparison Testing means comparing your software with the better one or you’re Competitor.
While comparison Testing we basically compare the Performance of the software. For ex If you have to do Comparison Testing of PDF converter(Desktop Based Application) then you will compare your software with your Competitor on the basis of:-
1. Speed of Conversion PDF file into Word.
2. Quality of converted file.
69. What is the general testing
process?
Testing Process:
1. Test requirements analysis
2. Creation of Test Strategy (Which includes creation of Test Cases)
3. Creation of Test Plans (Which includes Test Cases and Test Procedures)
4. Execution of test cases
5. Analyze the test results
6. Report the defects if any
Testing Process:
1. Test requirements analysis
2. Creation of Test Strategy (Which includes creation of Test Cases)
3. Creation of Test Plans (Which includes Test Cases and Test Procedures)
4. Execution of test cases
5. Analyze the test results
6. Report the defects if any
70. What participation a manual
tester can do in documentation? Are there any tools available for only
documentation?
Yes, Manual tester will do Sub Test plan documents, as of my knowledge no tool is used to prepare documentation
Yes, Manual tester will do Sub Test plan documents, as of my knowledge no tool is used to prepare documentation
71. What is the difference between
low and high level test cases? Give Examples?
High level Test cases are those which covers major functionality in the application (i.e. retrieve, update display, cancel (functionality related test cases), database test cases).
Low level test cases are those which are related to UI related testcases.
72. Is it mandatory to use USECASES or directly one can write test cases from requirements?
It’s not mandatory to write Use Cases, if the requirements are clear you can go ahead with Test Cases. Use Cases are written to know the business flow of the module/application.
High level Test cases are those which covers major functionality in the application (i.e. retrieve, update display, cancel (functionality related test cases), database test cases).
Low level test cases are those which are related to UI related testcases.
72. Is it mandatory to use USECASES or directly one can write test cases from requirements?
It’s not mandatory to write Use Cases, if the requirements are clear you can go ahead with Test Cases. Use Cases are written to know the business flow of the module/application.
73. How does u develop test harness?
Test Environment Test Bed
Test Environment S/W and H/W
Test Bed: Test Documents like Test Plan Document, Test Case Document.
Test Environment means
• Test Bed installation and configuration
• Network connectivity’s
• All the Software/ tools Installation and configuration
• Coordination with Vendors and others
Test Environment Test Bed
Test Environment S/W and H/W
Test Bed: Test Documents like Test Plan Document, Test Case Document.
Test Environment means
• Test Bed installation and configuration
• Network connectivity’s
• All the Software/ tools Installation and configuration
• Coordination with Vendors and others
74. Given requirement collection doc,
tester can prepare which test plan?
Test lead can prepare a test plan which performs testing on an application in an efficient effective and in an optimized way. Test development will done by the testers using the test
Plan in the test plan they prepare the test strategy
Test lead can prepare a test plan which performs testing on an application in an efficient effective and in an optimized way. Test development will done by the testers using the test
Plan in the test plan they prepare the test strategy
75. Tester with develop meant knowledge will be more effective .justify?
If tester has experience in Development, it will be useful when testing for logical thinking where the error occurs, what is the cause? He can guess the functionality of component? He can easily understand the application environment? Those are plus points which people have
Development experience.
Precisely he can justify that either functionality is wrong or right and can analyze the defects
76.As far as the SDLC is concerned
last test case,will it be written for “Maintenance Phase”?
As far as the SDLC is concerned last test case will be written for “Acceptance Testing”
As far as the SDLC is concerned last test case will be written for “Acceptance Testing”
77. What is test scenario and test
case? Please explain in detail?
Test Scenario:
Test scenario is like laying out plans for testing the product, environmental condition, number of team members required, making test plans, making test cases and what all features are to be tested for the product. Test scenario is very much dependent on the product to be tested.
Test scenario is made before the actual testing starts.
Test Case:
Test case is a document which provides the steps to be executed which has been planned earlier. It also depends on the type of product to be tested. Number of test cases is
Not fixed for any product.
Test Scenario:
Test scenario is like laying out plans for testing the product, environmental condition, number of team members required, making test plans, making test cases and what all features are to be tested for the product. Test scenario is very much dependent on the product to be tested.
Test scenario is made before the actual testing starts.
Test Case:
Test case is a document which provides the steps to be executed which has been planned earlier. It also depends on the type of product to be tested. Number of test cases is
Not fixed for any product.
78. What is the difference between
Project Based Testing and Product Based Testing?
Project based is nothing but client requirements. Product based is nothing but market requirements. Ex.stiching shirt is a project based and ready made shirt is product based.
Project based is nothing but client requirements. Product based is nothing but market requirements. Ex.stiching shirt is a project based and ready made shirt is product based.
80. What is testing process in
related to Application testing process is the one which tells you how the
application should be tested in order to minimize the bugs in the application?
One main thing no application can be released as bug free application which is impossible.
81. What is the difference b/n Testing Methodology and Testing methods?
Testing Methodology define process, set of rules and principle which are follow by group concerned with testing the application. Here I explain 7 step testing methodology:
1. Test Requirement Analysis
2. Test Plan
3. Test Design
4. Test execute
5. Defect track
6. Test Automation
7. Test Maintain
Testing methods or we can say that Testing Techniques:
White Box Testing (Unit Testing, Integration Testing)
Black Box Testing (System Testing, Functional Testing, Performance Testing>Load testing>stress testing>volume testing & Security Testing) UAT (done by user/client with actual/live data)
One main thing no application can be released as bug free application which is impossible.
81. What is the difference b/n Testing Methodology and Testing methods?
Testing Methodology define process, set of rules and principle which are follow by group concerned with testing the application. Here I explain 7 step testing methodology:
1. Test Requirement Analysis
2. Test Plan
3. Test Design
4. Test execute
5. Defect track
6. Test Automation
7. Test Maintain
Testing methods or we can say that Testing Techniques:
White Box Testing (Unit Testing, Integration Testing)
Black Box Testing (System Testing, Functional Testing, Performance Testing>Load testing>stress testing>volume testing & Security Testing) UAT (done by user/client with actual/live data)
82. What are starting links to test
while website testing?
Web based systems are those using the internet, intranet and extranets Web based testing only needs be done once for any applications using the web. Web based testing are as follows:
1. Functional correctness
2. Integration
3. Usability
4. Security
5. Performance
6. Verification of code
Web based systems are those using the internet, intranet and extranets Web based testing only needs be done once for any applications using the web. Web based testing are as follows:
1. Functional correctness
2. Integration
3. Usability
4. Security
5. Performance
6. Verification of code
83. How GUI testing will be done in
manual testing for a website?
For any testing there should be some set of standards to be followed. Particularly in GUI testing, look and feel should be good. We should follow the requirements specification documents for GUI testing.
There should be some screen shots (given by client) which we should follow as it is.
And for button sizes, font, font size ,colors used, placing of links, objects and the placing of the objects in the page should be followed some standards. If we take a button in the page that should be some standard size. If the size of that button is more or less the client feel bad about that. So we should have minimum common since while testing GUI testing. Some time there may be some mistakes in the screen shots provided by the client also, but that is our responsibility to raise those issues.
For any testing there should be some set of standards to be followed. Particularly in GUI testing, look and feel should be good. We should follow the requirements specification documents for GUI testing.
There should be some screen shots (given by client) which we should follow as it is.
And for button sizes, font, font size ,colors used, placing of links, objects and the placing of the objects in the page should be followed some standards. If we take a button in the page that should be some standard size. If the size of that button is more or less the client feel bad about that. So we should have minimum common since while testing GUI testing. Some time there may be some mistakes in the screen shots provided by the client also, but that is our responsibility to raise those issues.
84. What things should be tested in
regression testing?
While doing Regression Testing a tester must check that any new updating or Modification or Change in Functionality of a Particular Component or Module does not create any disorder and any negative affects on the functionality of the Application
While doing Regression Testing a tester must check that any new updating or Modification or Change in Functionality of a Particular Component or Module does not create any disorder and any negative affects on the functionality of the Application
85. What is the document required to
prepare during testing?
Normally Test engineers are responsible for any release of a project. Even the release is for staging environment or change request release or production release
The minimum documents are
1. Test Plan
2. Test Cases
3. Test Case Report
4. Bug report.
5. Release notes (which contains known issues).
6. Installation document.
Normally Test engineers are responsible for any release of a project. Even the release is for staging environment or change request release or production release
The minimum documents are
1. Test Plan
2. Test Cases
3. Test Case Report
4. Bug report.
5. Release notes (which contains known issues).
6. Installation document.
86. What is Test data? Where we are
using this in testing process?
What is the importance of this data?
To execute test cases we should have test data. This test data should be for positive and negative testings.for win runner we can get this test data from keyboard, excel sheets or from data base
What is the importance of this data?
To execute test cases we should have test data. This test data should be for positive and negative testings.for win runner we can get this test data from keyboard, excel sheets or from data base
87. What is the difference between
test case and test script?
Test case is a description what data to be tested and what data to be inserted what are the actions to be done to check actual result against expected result what are the actual inputs we will use? What are the expected results? Is called test script
Test Script: Is a short program written in a programming language used to test part of the functionality of the software system. A written set of steps that should be performed manually
Can also be called a test script; however this is more correctly called a test case.
Test case is a description what data to be tested and what data to be inserted what are the actions to be done to check actual result against expected result what are the actual inputs we will use? What are the expected results? Is called test script
Test Script: Is a short program written in a programming language used to test part of the functionality of the software system. A written set of steps that should be performed manually
Can also be called a test script; however this is more correctly called a test case.
89. What is the difference between
bug, error and defect?
At the time of coding mistake error, when the mistake noticed by the tester defect, tester sends this defect to development team if the developer agrees then it is bug
At the time of coding mistake error, when the mistake noticed by the tester defect, tester sends this defect to development team if the developer agrees then it is bug
90. What is the difference between
quality assurance and system testing explains in detail with an example?
Quality Assurance: It is nothing but building an adequate confidence in the customer that the developed software is acceding to requirements. Entire SDLC comes under QA. It is process oriented.
System Testing: It is the process of executing entire system i.e. checking the s/w as well as parts of system.
Quality Assurance: It is nothing but building an adequate confidence in the customer that the developed software is acceding to requirements. Entire SDLC comes under QA. It is process oriented.
System Testing: It is the process of executing entire system i.e. checking the s/w as well as parts of system.
91. How do you decide when you have ‘tested enough’?
When the 90% of requirements are covered, Maximum defects are rectified except (some) low level defects are not covered, customer satisfy that project and time is less, then we are closing the testing.
92. What is the difference between
Build Management and Release Management?
When will conduct build verification and end to end testing?
Build Management is managing the issue fixture tasks in the builds whereas Release management is managing the functionality to be incorporated in the Release.
Build Verification Test (BVT) is done when the build is first received by the testers. The basic functionality is checked with valid data. This is done to check whether the build is testable or not. This is done by testers.
End to End testing is also called system testing. Done by senior test engineers or Test lead.
When will conduct build verification and end to end testing?
Build Management is managing the issue fixture tasks in the builds whereas Release management is managing the functionality to be incorporated in the Release.
Build Verification Test (BVT) is done when the build is first received by the testers. The basic functionality is checked with valid data. This is done to check whether the build is testable or not. This is done by testers.
End to End testing is also called system testing. Done by senior test engineers or Test lead.
93. What is boundary value analysis
(BVA)? What is the use of it?
Boundary value analysis is a technique for test data selection. Test engineer chooses the values that lie along the data extreams.It includes max, minimum, just inside, just out side, typical values and error values.
Boundary Value Analysis is a technique used for writing the test cases. For example: If a particular field accepts the
Values from 1 to 1000, then we test that field by entering only 1, 1000, 0, 1001, 999, 2.
I.e. we check on the boundaries and then
Minimum-1, minimum +1 and maximum+1, maximum-1.
Boundary value analysis is a technique for test data selection. Test engineer chooses the values that lie along the data extreams.It includes max, minimum, just inside, just out side, typical values and error values.
Boundary Value Analysis is a technique used for writing the test cases. For example: If a particular field accepts the
Values from 1 to 1000, then we test that field by entering only 1, 1000, 0, 1001, 999, 2.
I.e. we check on the boundaries and then
Minimum-1, minimum +1 and maximum+1, maximum-1.
94. What is equivalence class
partition(ECP)? What is the use of it?
Aquaplane nothing but select the valid and valid class’s example as per client requirement the edit box access only
3-5 capital alphabets then we divided in esp. like valid values only A-Z invalid values are a-z and special characters like ^,8<%
Aquaplane nothing but select the valid and valid class’s example as per client requirement the edit box access only
3-5 capital alphabets then we divided in esp. like valid values only A-Z invalid values are a-z and special characters like ^,8<%
95. If there is no sufficient time for
testing & u have to complete the testing, then what will u do?
When I have less time to test the Product then I will take these following steps—
1) Sanity or smoke testing
2) Usability Testing
3) Formal Functionality and GUI Testing
4) Walk through with the Product
When I have less time to test the Product then I will take these following steps—
1) Sanity or smoke testing
2) Usability Testing
3) Formal Functionality and GUI Testing
4) Walk through with the Product
96. What is meaning by prototype in
SDLC?
This is a cyclic version of the linear model. In this model, once the requirement analysis is done and the design for a prototype is made, the development process gets started. Once the prototype is created, it is given to the customer for evaluation. The customer tests the package and gives his/her feed back to the developer who refines the product according to the customer’s exact expectation. After a finite number of iterations, the final software package is
Given to the customer. In this methodology, the software is devolved as a result of periodic shuttling of information between the customer and developer. This is the most popular development model in the contemporary IT industry. Most of the successful software products have been developed using this model - as it is very difficult (even for a whiz kid!)
To comprehend all the requirements of a customer in one shot. There are many variations of this model skewed with respect to the project management styles of the companies.
New versions of a software product evolve as a result of prototyping.
This is a cyclic version of the linear model. In this model, once the requirement analysis is done and the design for a prototype is made, the development process gets started. Once the prototype is created, it is given to the customer for evaluation. The customer tests the package and gives his/her feed back to the developer who refines the product according to the customer’s exact expectation. After a finite number of iterations, the final software package is
Given to the customer. In this methodology, the software is devolved as a result of periodic shuttling of information between the customer and developer. This is the most popular development model in the contemporary IT industry. Most of the successful software products have been developed using this model - as it is very difficult (even for a whiz kid!)
To comprehend all the requirements of a customer in one shot. There are many variations of this model skewed with respect to the project management styles of the companies.
New versions of a software product evolve as a result of prototyping.
97. What is difference between
desktop and web application?
The biggest d/f b/w Desktop and web application is- Desktop App (DA) is the machine independent, hence every change has only reflects at the machine level. Where as Web App (WA) is the Internet dependent program, hence any change in the program reflects at every where, where it becomes use. EX……
Suppose there are 5 machines in DA, 5 times installed individually at every machine and if there is any change made in DA then at every machine change has to be made. In WA where the program or Application at the Server or at the one common machine, then if changes made at only central or server or common machine all the changes get reflected at
Every client machine.
The biggest d/f b/w Desktop and web application is- Desktop App (DA) is the machine independent, hence every change has only reflects at the machine level. Where as Web App (WA) is the Internet dependent program, hence any change in the program reflects at every where, where it becomes use. EX……
Suppose there are 5 machines in DA, 5 times installed individually at every machine and if there is any change made in DA then at every machine change has to be made. In WA where the program or Application at the Server or at the one common machine, then if changes made at only central or server or common machine all the changes get reflected at
Every client machine.
98. Difference between application
testing and product testing?
Product testing means when any company does testing for their own (company’s) product ex… Norton Antivirus is the Symantec’s product; if Symantec test the Norton i.e. called
As the Product testing. Where as if any company take some projects from some other
Companies like ABC Company takes projects from IBM and test that project on some charges i.e. called as Application Testing.
Product testing means when any company does testing for their own (company’s) product ex… Norton Antivirus is the Symantec’s product; if Symantec test the Norton i.e. called
As the Product testing. Where as if any company take some projects from some other
Companies like ABC Company takes projects from IBM and test that project on some charges i.e. called as Application Testing.
99. What is a broken link in web
testing and how test it?
When we clicked on Hyper link if it opens Page can’t be displayed then that Hyper link is called as broken link.
When we clicked on Hyper link if it opens Page can’t be displayed then that Hyper link is called as broken link.
100: What is CMM level? I need the
answer in detail.
The Capability Maturity Model for
Software describes the principles and practices underlying software process
maturity and is intended to help software organizations improve the maturity of
their software processes in terms of an evolutionary path from ad hoc chaotic
processes to mature disciplined software processes. The CMM is organized into
five maturity levels
101: Difference between Project Risk
and Product Risk
Product Risks
As testers one of our tasks is to manage Product Risks.
As testers one of our tasks is to manage Product Risks.
We are paid (at least in part) to be
aware of all Product Risks, to make sure the rest of the project team is also
aware of them, and to coordinate this information with Project Management to
make sure our schedules are taking these risks into account.
In addition, we are expected to plan our testing strategy based on these risk, scheduling more tests (and earlier tests) on areas with higher risks in order to find these issues faster.
In addition, we are expected to plan our testing strategy based on these risk, scheduling more tests (and earlier tests) on areas with higher risks in order to find these issues faster.
My preferred method for handling
Product Risks starts by listing them as part of my MTP and reviewing them with
all the Project Stakeholders. During these reviews I try to get inputs into the
relevance of these risks, as well as information about additional risks I may
be unaware off. Once the project starts we review and update all product risks
as part of the coordination meetings with the rest of the project team.
Examples of Product Risks are:
- Complex features affecting multiple areas of the existing product, like an upgrade/migration of the system.
- New Technologies used in the product; for example a new DB server, a new programming language, a new integration, etc.
- New Developers or Development Teams, who may lack experience and thus pose a higher risk to the existing product.
- Tight Schedules, that make people work in a rush and commit more mistakes.
etc
- Complex features affecting multiple areas of the existing product, like an upgrade/migration of the system.
- New Technologies used in the product; for example a new DB server, a new programming language, a new integration, etc.
- New Developers or Development Teams, who may lack experience and thus pose a higher risk to the existing product.
- Tight Schedules, that make people work in a rush and commit more mistakes.
etc
Project Risks
The responsible for Project Risks are the Project Managers, who are also in charge of the project’s schedule. The QA, as part of the overall team, is responsible for the Project Risks within our work areas.
The responsible for Project Risks are the Project Managers, who are also in charge of the project’s schedule. The QA, as part of the overall team, is responsible for the Project Risks within our work areas.
Project Risks are usually managed in
an Excel Sheet (or Google Docs Spreadsheet) where we list and manage all the
risks for the project. For each risk we collect and manage the following
information:
1. Risk Name & Description
2. Risk Index (we use this field in order to sort our list) – calculated by multiplying its probability by its consequence
3. Risk owner
4. Date of relevance – when does the risk starts been relevant and prevention actions can start taking place
5. Prevention Actions – how to avoid this risk
6. Contingency Plans – what do we do if the risk materializes
1. Risk Name & Description
2. Risk Index (we use this field in order to sort our list) – calculated by multiplying its probability by its consequence
3. Risk owner
4. Date of relevance – when does the risk starts been relevant and prevention actions can start taking place
5. Prevention Actions – how to avoid this risk
6. Contingency Plans – what do we do if the risk materializes
The most usual project risks related
to the QA & Testing work are:
- Delays in the delivery of the AUT for testing
- Lack of technical knowledge on specific areas of the product
- Lack of testing environments and/or data that effectively simulate real customer usage
etc.
- Delays in the delivery of the AUT for testing
- Lack of technical knowledge on specific areas of the product
- Lack of testing environments and/or data that effectively simulate real customer usage
etc.
Risks are a big part of any manager’s
work. We are expected to be in the lookout for the things that may happen and
prepare accordingly.
Most of the task related to Risk
Management are not complex but they require good understanding of the project
and product as well as the strict discipline required to keep following and
managing these risks throughout the whole lifecycle of the project.
102: If one of the bug Find by you ?
but same bug it didn't find on developer computer ? what would you do ?
When you found a bug and developer is
not able reproduce it on his system please do the below things
1.
Check
the version you have in QA and Developer has
2.
If
both the versions are same, then provide the steps to him in details to what to
do step by step and also clearly mention that what you are doing before every
click.. ex: entering data into few fields and kind of data you entered,
selecting data from drop downs
3.
Still
if he is not able to reproduce, then check the OS, Browser, version of the
browser etc…
4.
If
still the issue is not reproducible, go to developer’s desk and try to
reproduce
5.
Still
if you are not able to reproduce, then check in your QA once again to find the
cause of the issue.. if you could find it why it is only happening in QA (
there might be, build deployment issue, or data issue etc…)
6.
Still
if you are not able to find the right cause.. then add a comment saying that,
still this issue occurs in QA environment but not in Dev leave it open till end
of the project and have a discussion with BA, PM and come to a conclusion on
what to do with that ( final solution might be, leaving it OPEN or Closed with
agreement between all the parties)
4. If still the issue is not
reproducible, go to developer’s desk and try to reproduce
5. Still if you are not able
to reproduce, then check in your QA once again to find the cause of the issue..
if you could find it why it is only happening in QA ( there might be, build
deployment issue, or data issue etc…)
6. Still if you are not able
to find the right cause.. then add a comment saying that, still this issue
occurs in QA environment but not in Dev leave it open till end of the project
and have a discussion with BA, PM and come to a conclusion on what to do with
that ( final solution might be, leaving it OPEN or Closed with agreement
between all the parties)
In addition, we are expected to plan our testing strategy based on these risk, scheduling more tests (and earlier tests) on areas with higher risks in order to find these issues faster.
My preferred method for handling Product Risks starts by listing them as part of my MTP and reviewing them with all the Project Stakeholders. During these reviews I try to get inputs into the relevance of these risks, as well as information about additional risks I may be unaware off. Once the project starts we review and update all product risks as part of the coordination meetings with the rest of the project team.
Examples of Product Risks are:
- Complex features affecting multiple areas of the existing product, like an upgrade/migration of the system.
- New Technologies used in the product; for example a new DB server, a new programming language, a new integration, etc.
- New Developers or Development Teams, who may lack experience and thus pose a higher risk to the existing product.
- Tight Schedules, that make people work in a rush and commit more mistakes.
etc
- Complex features affecting multiple areas of the existing product, like an upgrade/migration of the system.
- New Technologies used in the product; for example a new DB server, a new programming language, a new integration, etc.
- New Developers or Development Teams, who may lack experience and thus pose a higher risk to the existing product.
- Tight Schedules, that make people work in a rush and commit more mistakes.
etc
Project Risks
The responsible for Project Risks are the Project Managers, who are also in charge of the project’s schedule. The QA, as part of the overall team, is responsible for the Project Risks within our work areas.
The responsible for Project Risks are the Project Managers, who are also in charge of the project’s schedule. The QA, as part of the overall team, is responsible for the Project Risks within our work areas.
Project Risks are usually managed in an Excel Sheet (or Google Docs Spreadsheet) where we list and manage all the risks for the project. For each risk we collect and manage the following information:
1. Risk Name & Description
2. Risk Index (we use this field in order to sort our list) – calculated by multiplying its probability by its consequence
3. Risk owner
4. Date of relevance – when does the risk starts been relevant and prevention actions can start taking place
5. Prevention Actions – how to avoid this risk
6. Contingency Plans – what do we do if the risk materializes
1. Risk Name & Description
2. Risk Index (we use this field in order to sort our list) – calculated by multiplying its probability by its consequence
3. Risk owner
4. Date of relevance – when does the risk starts been relevant and prevention actions can start taking place
5. Prevention Actions – how to avoid this risk
6. Contingency Plans – what do we do if the risk materializes
The most usual project risks related to the QA & Testing work are:
- Delays in the delivery of the AUT for testing
- Lack of technical knowledge on specific areas of the product
- Lack of testing environments and/or data that effectively simulate real customer usage
etc.
- Delays in the delivery of the AUT for testing
- Lack of technical knowledge on specific areas of the product
- Lack of testing environments and/or data that effectively simulate real customer usage
etc.
Risks are a big part of any manager’s work. We are expected to be in the lookout for the things that may happen and prepare accordingly.
Most of the task related to Risk Management are not complex but they require good understanding of the project and product as well as the strict discipline required to keep following and managing these risks throughout the whole lifecycle of the project.
102: If one of the bug Find by you ? but same bug it didn't find on developer computer ? what would you do ?
When you found a bug and developer is not able reproduce it on his system please do the below things
- Check the version you have in QA and Developer has
- If both the versions are same, then provide the steps to him in details to what to do step by step and also clearly mention that what you are doing before every click.. ex: entering data into few fields and kind of data you entered, selecting data from drop downs
- Still if he is not able to reproduce, then check the OS, Browser, version of the browser etc…
- If still the issue is not reproducible, go to developer’s desk and try to reproduce
- Still if you are not able to reproduce, then check in your QA once again to find the cause of the issue.. if you could find it why it is only happening in QA ( there might be, build deployment issue, or data issue etc…)
- Still if you are not able to find the right cause.. then add a comment saying that, still this issue occurs in QA environment but not in Dev leave it open till end of the project and have a discussion with BA, PM and come to a conclusion on what to do with that ( final solution might be, leaving it OPEN or Closed with agreement between all the parties)
No comments:
Post a Comment