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.
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.
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.
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.
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
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.
The major difference between them are: Web Services: Its more towards the internet side. When we talk about web services it could mean from the java side (deployed on Apache) or Windows side (deployed on IIS). Testing web services is totally a different topic here. Client Server: The system here involves a client system or a GUI (wherein a user see the front end by which he can input to the system) and a Server ( a backend usually) where in the data gets saved via the GUI
purpose of software testing's is to detect the Bug , System's functionality working will be smooth , and the job is done with full quality. purpose of software testing is to detect bugs and then report those bugs to the development team to fix those bugs and test the functionality as well as interdependence of modules and finaly the quality assurance.
Quality: The degree to which a product performs as advertised, without flaws and without unnecessary complications Also for finding bugs and making sure they (bugs)get fixed and stay fixed. Quality means - 1. For the development team - meeting all the requirements specifications. 2. For customers - Fit for use.
A bug is a defect in software that causes that same software to fail to comply to a given specification. You have two types of bugs:
1) code error related bugs and
2) design error related bugs the test bugs are those which can found in source code or in earier stage in like in desiging or some time in the requirements collection if the interact between customer and domain comany people is missing.
35% of the development time (time taken for analysis and coding)should be allocated for the testing process.
Bug: The problem getting at the time of testing. Defect: when we get problem on customer's hand is a defect. Defect:Tester found a mismatch during testing time is called as defect. Bug:tester found defect is accepted by tracking team and developer ready to fix is called as bug
First step : Bug finding Second Step : Bug Reporting Third Step : Bug De-bugging(fixing) Fourth Step : Re verification of the reported bug (Regression) This is the process of Bug cycle
Exceptions are errors thrown by the programmer errors occurs in runtime and seen by the user
I think it is not Matrix..it is Metrics.Traceability Metrics is a proof of document to ensure that all the specifications are been tested and the application is bug free.The Traceability metrics Includes The following Details:BRD#FS#TEST CASE#DESCRIPTIONTESTERTEST SETUPPASSED/FAILEDDEFFECTSTATUS OF DEFFECTETC.There are different metices are used to figure out how the QA is going about the testing.Test case execution metricsScript metricsRequirements metricsDeffects tracking metrics.The metrics are also used as Map among differe System features,Test cases,Modules and so on.ex: it is very easy to find who is responsible for deffect id
1009 in Login module for BRD
System testing is the phase of software testing in which the complete system is tested. It follows Integration testing. End to End testing is the testing of the application for all the possible scenarios. It is someway related to Exhaustive testing of the application. however, this can not be done in practise as they are more time consuming.
Test Procedure is a part of Test Case document.It comprises of following three steps:
1. To verify the look and feel of AUT through GUI test cases.
2. To verify the positive behavior of AUT through positive test cases.
3. To veify the neative behaviour of the AUT through negative test cases.
When we find out the bug, we will put into the “open” status. After fixing the bug developer change the status as “fixed”. Again we will test the fixed part, if there is no bug, change the bug status as “Closed” other wise change the bug status as “Reopen”. A s/w metric defines the a standard method of measuring certain attributes of the process or the product or the service.
Based on the budjet for the project; the time frame; number of members in the team and based on how huge the project is; whether it has some version control or version change; the company will decide the start of the project.
In my company i prepare three type of test cases they are,
1)graphical user interface testcases(gui test cases)
2)positive test cases
3)negative test cases
All major MNCs are used the functional tools are:
Win runner, QTP and some companies are used Silk test.
For management tools , 'Test director' mostly used.
For load testing, Load Runner is using.
Following methods are commonly used for writing test cases.
* Equavalence partitioning.
* Boundry value analysis
* Based on past experience.
Phase Containment is incorporating QA into all the phases of SDLC. It results in Defect Prevention. If Qa team performs Requirements Review, Design Review and Code Review, defects would be few when actual application is tested. That means we have prevented many defects by performing reviews at each stage of SDLC.
SQA means Software Quality Assurance.It is the process of implementing and monitoring the entire SDLC process. In this we have 4 phases 1.Analysis 2.Design 3.Coding 4.Testing
Test Plan Have these major contants:
2 Resource need
5 Feature to be tested with reason
6 feature not to be tested with reason 5 Test stratergy
6 Scope of testing
7 Tools to be used
Yes I have converted Test scenarios into Test cases. From FD write Test Scenarios and Test Conditions After these two writing test case accordingly
According to me Technical environments depends on compay to company and also on the compatability of project like most of the projects supports Windows and 3 - tire application in case of Database or some s/w will work on Unix / Linux so answer for this will different for different users
sanity testign is also called as Build verification testing. Every Build release from developer should be followed by sanity testing. - In sanity testing we install the application, launch the application and navigate through the application. - Sanity test is implemented to make sure the application is ready for complete testing. Every Build release to the client should be preceded by smoke testing. - smoke testing is implemented to make sure the application given to the client on the final release media is working fine, - smoke testing will be a quick test phase to test installation, launching and basic functionality navigation. - smoke testing is carried out using the check lists. -smoke testing is carried out before every release to the client.
Yes we can,but you can not have a full flow on that test case.because BRD and use cases used to prepare FRS.with help of FRS we can write our testcase.
There is no particular bug tracking tool. It will vary from company to company. In my company they are using Bugzilla. In some comp use TD, Service Point, manita1.0.1, Test Team, etc..
Install Shield is the software which is used to create the setup files. There is Installation testing which ensures that the user can install the software without any problem and the files are getting stored at proper place and all the register entry are getting stored properly. There is nothing called Installation Shield testing.
Difference between test case and use case is use case is prepared by High Level Management team but test case is prepared by Test engineers. Use case is prepared for validating the applications in terms of Actors, actions and responses but test case is used to test a specific functionality of an application.
The difference between the expected value and the actual value is called a bug .
The main focus while writing test cases should be to cover all the documented requirements, a rudimentary form of doing this is by specifying the exact requirement number/id against every test case. A better way of doing this is by preparing a Traceability Matrix We should also try and write which cover the implicit requirements along with the expliocit stated ones, some negative test cases to cover unpredicatable scenarios. Effort should be made to test all possible inputs and to apply whatever domain knowledge the tester has. The test cases should follow a logical flow, and should include all the information required for executing the steps. The writing style should be easy to understand, all these points make it easy for the reviewer to review the test cases, and also help in easy execution of test cases as they might be executed by another person. The template for writing the test cases should also be followed preperly and all columns should be filled in with the required information.
DIFFERENCE BETWEEN THE GUI TESTING AND BLACK BOX TESTING GUI TESTING MAINLY TEST THE APPLICATION OBJECTS LIKE BUTTONS,TEXT BOXES,CHECK BOXES ETC., BLACK BOX TESTING MAINLY TEST THE APPLICATION FUNCTIONALITY.
Test case analysis means reviewing the test case normally done by team lead or Quality Manager. In this process he / she walkthorugh the testccases and compares with the SRS or functional document and also checks whether all major scenarios were considered by test engineer while writting the test case and informs accordingly.
Several standards suggest what a test plan should contain, including the IEEE. The standards are: IEEE standards: 829-1983 IEEE Standard for Software Test Documentation 1008-1987 IEEE Standard for Software Unit Testing 1012-1986 IEEE Standard for Software Verification & Validation Plans 1059-1993 IEEE Guide for Software Verification & Validation Plans
No. Currently, not supported.
DTD stands for document type definition. it describes elements that appear in the XML document what are its contents and attributes Reply With Quote