Define Test Specifications?
The Test case specifications should be developed from the test plan and are the second phase of the test development life cycle. The test specification should explain "how" to implement the test cases described in the test plan.
Test Specification Items Each test specification should contain the following items :
> Case No : The test case number should be a three digit identifer of the following form: c.s.t,
> where : c- is the chapter number, s- is the section number, and t- is the test case number.
> Title : is the title of the test.
> ProgName : is the program name containing the test.
> Author : is the person who wrote the test specification.
> Date : is the date of the last revision to the test case.
> Background : (Objectives, Assumptions, References, Success Criteria) : Describes in words how to conduct the test.
> Expected Error(s) : Describes any errors expected.
> Reference(s) : Lists reference documententation used to design the specification.
> Data : (Tx Data, Predicted Rx Data): Describes the data flows between the Implementation Under Test (IUT) and the test engine.
> Script : (Pseudo Code for Coding Tests): Pseudo code (or real code) used to conduct the test.
Example Test Specification
> Title : Invalid Sequence Number (TC)
ProgName : Background : (Objectives, Assumptions, References, Success Criteria)
Validate that the IUT will reject a normal flow PIU with a transmissionheader that has an invalid sequence number.
Data: (Tx Data, Predicted Rx Data)
<-------- DATA FIS, OIC, DR1 SNF=20
<-------- DATA LIS, SNF=20
--------> -RSP $2001
> Script : (Pseudo Code for Coding Tests)
SEND_PIU FIS, OIC, DR1, DRI SNF=20
SEND_PIU LIS, SNF=20
What SQL statements have you used in Database Testing?
The most important statement for database testing is the SELECT statement, which returns data rows from one or multiple tables that satisfies a given set of criteria. We may need to use other DML (Data Manipulation Language) statements like INSERT, UPDATE and DELTE to manage our test data.
We may also need to use DDL (Data Definition Language) statements like CREATE TABLE, ALTER TABLE, and DROP TABLE to manage our test tables.
We may also need to some other commands to view table structures, column definitions, indexes, constraints and store procedures.Reply
define : Formal Technical Review: Reviews that include walkthroughs, inspection?
Reviews that include walkthroughs, inspection, round-robin reviews and other small group technical assessment of software. It is a planned and control meeting attended by the analyst, programmers and people involve in the software development.
> Uncover errors in logic, function or implementation for any representation of software,
> To verify that the software under review meets the requirements.
> To ensure that the software has been represented according to predefined standards.
> To achieve software that is developed in a uniform manner.
> To make project more manageable.
> Early discovery of software defects, so that in the development and maintenance phase the errors are substantially reduced. " Serves as a training ground, enabling junior members to observe the different approaches in the software development phases (gives them helicopter view of what other are doing when developing the software).
> Allows for continuity and backup of the project. This is because a number of people are become familiar with parts of the software that they might not have otherwise seen.
> Greater cohesion between different developers. Reply
How can I check if a checkpoint passes or not?
chk_PassFail = Browser(...).Page(...).WebEdit(...).Check (Checkpoint("Check1"))
if chk_PassFail then
MsgBox "Check Point passed"
MsgBox "Check Point failed"
end if Reply
Define : Reluctance of implementing Software Quality Assurance?
Managers are reluctant to incur the extra upfront cost Such upfront cost are not budgeted in software development therefore management may be unprepared to fork out the money.
> Avoid Red : Tape (Bureaucracy)
> Red tape means extra administrative activities that needs to be performed as SQA involves a lot of paper work. New procedures to determine that software quality is correctly implemented needs to be developed, followed through and verified by external auditing bodies. These requirements involves a lot of administrative paperwork.Reply
What is the mean of Constraints of Software Quality Assurance??
Difficult to institute in small organizations where available resources to perform the necessary activities are not present. A smaller organization tends not to have the required resources like manpower, capital etc to assist in the process of SQA. Cost not budgeted In addition , SQA requires the expenditure of dollars that are not otherwise explicitly budgeted to software engineering and software quality. The implementation of SQA involves immediate upfront costs, and the benefits of SQA tend to be more long-term than short-term. Hence, some organizations may be less willing to include the cost of implementing SQA into their budget.Reply
What is way of writing testcases for database testing?
Many ways are there :
We have to do the following for writing the database testcases.
1. First of all we have to understand the functional requirement of the application throughly.
2. Then we have to find out the back end tables used, joined used between the tables, cursors used, tiggers used, stored procedures used, input parmeter used and output parameters used for developing that requirement.
3. After knowing all these things we have to write the testcase with different input values for checking all the paths of SP. One thing writing testcases for backend testing not like functinal testing. We have to use white box testing techniques. To write testcase for database its just like functional testing.
1. Objective : Write the objective that you would like to test. eg: To check the shipment that i load thru xml is getting inserted for perticular customer.
2. Write the method of input or action that you do. eg: Load an xml with all data which can be added to a customer.
3. Expected : Input should be viewd in database. eg: The shipment should be loaded sucessfully for that customer,also it should be seen in application.
4. We can write ssuch type of testcases for any functionality like update,delete etc.
>>> At first we need to go through the documents provided. Need to know what tables, stored procedures are mentioned in the doc.Then test the functionality of the application. Simultaneously, start writing the DB testcases.. with the queries we have used at the backend while testing, the tables and stored procedures we have used in order to get the desired results. Trigers that were fired. Based on the stored procedure we can know the functionality for a specific peice of the application. So that we can write queries related to that. From that we make DB testcases also.Reply
How can I import environment from a file on disk?
Environment.LoadFromFile "C:Env.xml" Reply
What we normally check for in the Database Testing?
In DB testing we need to check for :
A. The field size validation
B. Check constraints.
C. Indexes are done or not (for performance related issues)
D. Stored procedures
E. The field size defined in the application is matching with that in the db. Database testing involves some indepth knowledge of the given application and requires more defined plan of approach to test the data. Key issues include :
> data Integrity
> data validity
> data manipulation and updates.
Tester must be aware of the database design concepts and implementation rules.Reply
How can I check if a environment variable exist or not?
When we use Environment("Param1").value then QTP expects the environment variable to be already defined. But when we use Environment.value("Param1") then QTP will create a new internal environment variable if it does not exists already. So to be sure that variable exist in the environment try using Environment("Param1").value.Reply