31. 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.
32. How does u develop test harness?
1. Test Environment Test Bed
2. Test Environment S/W and H/W
3. Test Bed: Test Documents like Test Plan Document, Test Case Document.
4. Test Environment means
a. Test Bed installation and configuration
b. Network connectivity’s
c. All the Software/ tools Installation and configuration
d. Coordination with Vendors and others
33. Given requirement collection document, 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 do by the testers using the test. Plan in the test plan they prepare the test strategy.
34. 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.
35. 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”.
36. 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, and 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.
37. 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.
38. 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 manually.
39. 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:
· Information of Document,
· Description,
· Objective,
· Actors,
· Pre-conditions,
· Data-element descriptions,
· Post conditions,
· Primary flow,
· Alternative flow and Business rules/interaction implementations and etc….
40. What are the difference between stress, volume and load testing?
Load Testing gradually increases the load and checks the performance of the application. We check at what point or maximum load application can sustain.
Stress testing: In this testing we 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.
41. When will do the beta test? When will 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 is conducting for software application by real customer at development site.
Beta testing is conducting for software product by model customer at customer site.
42. 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.
43. Can you explain with example of high severity and low priority, low severity and high priority, high severity and high priority, low severity 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.
a. High priority & High Severity: If u clicks on explorer icon or any other icon then system crash.
b. Low priority & low severity: In login window, spell of ok button is “Ko”.
c. Low priority & high severity: 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.
d. High priority & low severity: Suppose logo of any brand company is not proper in their product. So it affects their business.
44. 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
7. Successful selection of account type
8. Un successful operation due to invalid account type
9. Successful selection of withdraw operation
10. Successful selection of amount to be withdraw
11. Successful withdraw operation
12. Unsuccessful withdraw operation due to wrong denominations
13. Unsuccessful withdraw operation due to amount is greater than day limit
14. Unsuccessful withdraw operation due to lack of money in ATM
15. Unsuccessful withdraw operation due to amount is greater than possible balance
16. Unsuccessful withdraw operation due to transactions is greater than day limit
17. Unsuccessful withdraw operation due to click cancel after insert card
18. Unsuccessful withdraw operation due to click cancel after insert card & pin number
19. Unsuccessful withdraw operation due to click cancel after insert card, pin number & language
20. Unsuccessful withdraw operation due to click cancel after insert card, pin number, language & account type
21. Unsuccessful withdraw operation due to click cancel after insert card , pin number, language, account type & withdraw operation
22. Unsuccessful withdraw operation due to click cancel after insert card, pin number, language, account type, withdraw operation & amount to be withdraw
Test cases for Coffee Machine:
1. Plug the power cable and press the on button. The indicator bulb should glow indicating the machine is on.
2. Whether there are three different buttons Red Blue and Green.
3. Whether Red indicated Coffee.
4. Whether Blue indicated Tea.
5. Whether Green indicated Milk.
6. Whether each button produces the correct out put (Coffee Tea or Milk).
7. Whether the desired out put is hot or not (Coffee Tea or Milk).
8. Whether the quantity is exceeding the specified the limit of a cup.
9. Whether the power is off (including the power indicator) when pressed the off button.
45. Tell me about the daily activities as a test engineer?
The daily activities / role as a test engineer:
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.
46. 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 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
47. 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.
48. 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, Updation 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.
49. 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.
50. Difference between strategic test plan & test plan?
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.
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 organization.
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
51. Draw Backs of automated testing?
DRAW BACKS OF AUTMATION: Expensive, lack of expertisation, all the areas we can not automate
52. 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
53. 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.
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.
54. 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
55. 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, and 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 test case. Here are 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. Test cases on HOLD (Includes blocking test cases and deferred Test cases)
10. Coverage 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, achievements 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 are the contents covered in the Test Report:
1. Test Environment (Should be covered the OS, Application or web servers, Machine 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
a. Defects logged in different types of tests like Functional Test, regression Test as per area wised.
b. State of the Defects at end of the Test cycle.
c. Root cause analysis for the bugs marked as NOT A BUG.
7. QA observations or learning’s thought the life cycle.
56. 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.
HIGH LEVEL TEST CASE
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…
LOW LEVEL TEST CASE
1. Verify that after launching the URL of the application below fields are displays in the screen.
2. Login Name 3. Password. 4. OK BUTTON 5. RESET button etc.
3. Check box, provided for the label “remember my password” is unchecked.
4. Verify that OK button should be disabled before selecting login and password fields.
5. Verify that OK button should we enabled after selecting login and password.
6. Verify that User is able to check the check box, provided for the label “remember my password”.
Etc.
In this way, we can categories all the test cases under HIGH LEVEL and LOW LEVEL.
57. 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
58. 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.
59. 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 activities, which we are implementing for the better productivity. (As per the company’s standards). Here are some of the Test deliverables:
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.
60. 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 Test Plan. 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 Test Plan. But in most of the companies Test engineers are just audience.
61. 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
62. 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
63. 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.
64. 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
65. 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 are used. So stubs are small dummy modules that test the core module.
Driver testing: In bottom up approach, small modules are developed. To test them a dummy core module called driver is developed.
66. 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.
67. 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 you know the functionality covered or not you can use RTM.
68. 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.
69. 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 its connected modules are checked for their integrity after bug fixation.
70. 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
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.
32. How does u develop test harness?
1. Test Environment Test Bed
2. Test Environment S/W and H/W
3. Test Bed: Test Documents like Test Plan Document, Test Case Document.
4. Test Environment means
a. Test Bed installation and configuration
b. Network connectivity’s
c. All the Software/ tools Installation and configuration
d. Coordination with Vendors and others
33. Given requirement collection document, 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 do by the testers using the test. Plan in the test plan they prepare the test strategy.
34. 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.
35. 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”.
36. 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, and 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.
37. 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.
38. 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 manually.
39. 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:
· Information of Document,
· Description,
· Objective,
· Actors,
· Pre-conditions,
· Data-element descriptions,
· Post conditions,
· Primary flow,
· Alternative flow and Business rules/interaction implementations and etc….
40. What are the difference between stress, volume and load testing?
Load Testing gradually increases the load and checks the performance of the application. We check at what point or maximum load application can sustain.
Stress testing: In this testing we 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.
41. When will do the beta test? When will 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 is conducting for software application by real customer at development site.
Beta testing is conducting for software product by model customer at customer site.
42. 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.
43. Can you explain with example of high severity and low priority, low severity and high priority, high severity and high priority, low severity 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.
a. High priority & High Severity: If u clicks on explorer icon or any other icon then system crash.
b. Low priority & low severity: In login window, spell of ok button is “Ko”.
c. Low priority & high severity: 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.
d. High priority & low severity: Suppose logo of any brand company is not proper in their product. So it affects their business.
44. 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
7. Successful selection of account type
8. Un successful operation due to invalid account type
9. Successful selection of withdraw operation
10. Successful selection of amount to be withdraw
11. Successful withdraw operation
12. Unsuccessful withdraw operation due to wrong denominations
13. Unsuccessful withdraw operation due to amount is greater than day limit
14. Unsuccessful withdraw operation due to lack of money in ATM
15. Unsuccessful withdraw operation due to amount is greater than possible balance
16. Unsuccessful withdraw operation due to transactions is greater than day limit
17. Unsuccessful withdraw operation due to click cancel after insert card
18. Unsuccessful withdraw operation due to click cancel after insert card & pin number
19. Unsuccessful withdraw operation due to click cancel after insert card, pin number & language
20. Unsuccessful withdraw operation due to click cancel after insert card, pin number, language & account type
21. Unsuccessful withdraw operation due to click cancel after insert card , pin number, language, account type & withdraw operation
22. Unsuccessful withdraw operation due to click cancel after insert card, pin number, language, account type, withdraw operation & amount to be withdraw
Test cases for Coffee Machine:
1. Plug the power cable and press the on button. The indicator bulb should glow indicating the machine is on.
2. Whether there are three different buttons Red Blue and Green.
3. Whether Red indicated Coffee.
4. Whether Blue indicated Tea.
5. Whether Green indicated Milk.
6. Whether each button produces the correct out put (Coffee Tea or Milk).
7. Whether the desired out put is hot or not (Coffee Tea or Milk).
8. Whether the quantity is exceeding the specified the limit of a cup.
9. Whether the power is off (including the power indicator) when pressed the off button.
45. Tell me about the daily activities as a test engineer?
The daily activities / role as a test engineer:
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.
46. 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 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
47. 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.
48. 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, Updation 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.
49. 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.
50. Difference between strategic test plan & test plan?
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.
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 organization.
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
51. Draw Backs of automated testing?
DRAW BACKS OF AUTMATION: Expensive, lack of expertisation, all the areas we can not automate
52. 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
53. 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.
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.
54. 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
55. 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, and 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 test case. Here are 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. Test cases on HOLD (Includes blocking test cases and deferred Test cases)
10. Coverage 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, achievements 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 are the contents covered in the Test Report:
1. Test Environment (Should be covered the OS, Application or web servers, Machine 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
a. Defects logged in different types of tests like Functional Test, regression Test as per area wised.
b. State of the Defects at end of the Test cycle.
c. Root cause analysis for the bugs marked as NOT A BUG.
7. QA observations or learning’s thought the life cycle.
56. 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.
HIGH LEVEL TEST CASE
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…
LOW LEVEL TEST CASE
1. Verify that after launching the URL of the application below fields are displays in the screen.
2. Login Name 3. Password. 4. OK BUTTON 5. RESET button etc.
3. Check box, provided for the label “remember my password” is unchecked.
4. Verify that OK button should be disabled before selecting login and password fields.
5. Verify that OK button should we enabled after selecting login and password.
6. Verify that User is able to check the check box, provided for the label “remember my password”.
Etc.
In this way, we can categories all the test cases under HIGH LEVEL and LOW LEVEL.
57. 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
58. 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.
59. 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 activities, which we are implementing for the better productivity. (As per the company’s standards). Here are some of the Test deliverables:
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.
60. 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 Test Plan. 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 Test Plan. But in most of the companies Test engineers are just audience.
61. 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
62. 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
63. 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.
64. 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
65. 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 are used. So stubs are small dummy modules that test the core module.
Driver testing: In bottom up approach, small modules are developed. To test them a dummy core module called driver is developed.
66. 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.
67. 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 you know the functionality covered or not you can use RTM.
68. 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.
69. 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 its connected modules are checked for their integrity after bug fixation.
70. 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
No comments:
Post a Comment