1. Who will prepare the Tracebility Matrix?
Tester will prepare the tracebility matrix becoz he will author the test cases from requirements or use cases.
Test Plan: Test plan is a Document, developed by the Test Lead, which contains "What to Test","How to Test", "When to Test", "Who to Test". Test Strategy: Test Strategy is a Document, developed by the Project manager, which contains what type of technique to follow and which module to test. Test Scenario: A name given to Test Cases is called Test Scenario. These Test Scenario was deal bythe Test Enggineer. Test Cases:It is also document andit specifies a Testable condition to validate a functionality. These Test Cases are deal by the Test Enggneer Order of STLC: Test Strategy, Test Plan, Test Scenario, Test Cases. Test plan : Test plan is a Document, developed by the Test Lead, which contains "What to Test","How to Test", "When to Test", "Who to Test". Test Strategy: Test Strategy is a Document, developed by the Project manager, which contains what type of technique to follow and which module to test. Test Scenario: A name given to Test Cases is called Test Scenario. These Test Scenario was deal bythe Test Enggineer. Test Cases:It is also document andit specifies a Testable condition to validate a functionality. These Test Cases are deal by the Test Enggneer Order of STLC: Test Strategy, Test Plan, Test Scenario, Test Cases.
3. Have you worked with datapools and what is your opinion on them?
Data Pool is notheing but a parameterization.Here we can access the single output for different input values, which already defined in the code. Example, we want login the application with different user names, as this type of situation you have we use data pool . Datapools provide variable data to your tests during execution. Performance tests are based on user emulation. During a session with the application-under-test, the tester actually uses a feature that real customers will use, and from the recorded session a test is generated containing the exact data that the tester entered. For example, to create a performance test for a dialog in a web-based shopping application that prompts a shopper for an account number, the tester actually engages the dialog by selecting an item that is offered for sale, clicking a "pay now" button, and entering an account number. During playback of the test, in which the tester might request that hundreds of instances of the transaction be run simultaneously, it is desirable that different account numbers (perhaps a combination of valid and invalid numbers) are used for each of the instances. To supply variable data for tests to use during playback, the tester creates datapools.
4. What kind of things does one need to know before starting an automation project?
Before starting and automation project one has to know whether he/she 1.has the build(.exe) or not 2.whether the req tools are installed or not 3.should have the knowledge of the tools 4. what to test yah! At the same time, 1. we have to know the flow path of the execution. 2.Scenarios could be written. 3.Not all the test cases could be automated.only test cases which are critical to manual testing are automated. 4.For the project which is always having possiblility to release versions that are automated. 5.Tests which tested manually with diff.sets of data are automated. 6.By using logical methods(loops and functions)we can retrive the data from databases are going to be automated.
5. What is the difference between end to end testing and system testing?
System testing is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. end to end testing: here we give real time data... System Testing: One module or part of the system is tested end-to-end Testing: The entire project, i.e which has many integrated systems, are tested.
6. What is calability testing?
If it is Scalbilty testing , then Scalability testing can be performed as a series of load tests with different hardware or software configurations keeping other settings of testing environment unchanged. The purpose of scalability testing is to determine whether your application scales for the workload growth. Suppose your company expects a six-fold load increase on your server in the next two months. You may need to increase the server performance and to shorten the request processing time to better serve visitors. If your application is scalable, you can shorten this time by upgrading the server hardware, for example, you can increase the CPU frequency and add more RAM (also, you can increase the request performance by changing the server software, for example, by replacing the text-file data storages with SQL Server databases. To find a better solution, first you can test hardware changes, then software changes and after that compare the results of the tests).
Cost of solving a bug from requirements phase to testing phase - increases slowly
Finding the mean time b/w system failure and system recovery. We should take care of the following in reliability testing. Business logic performs as expected Active buttons are really active Correct menu options are available Reliable hyper links
9. What is Scalability Testing? Which tool is used?
The execution of project functionality under customer expected configuration and customer expected load to estimate the performance of the project is called load testing or scalability testing. LoadRunner, Winrunner, Astra, Rational Robot
There are some tool availble in the market like, Microsoft Project Management tool.
