HP QC SQL Queries

Test-lab:
SELECT CY_CYCLE AS "Test Set",
       TS_NAME AS "Test Script Name",
       TC_ACTUAL_TESTER AS "Tester",
       TC_STATUS AS "Execution Status",
       LEFT(CONVERT(VARCHAR,TC_EXEC_DATE,20),10)  AS "Execution Date"
FROM TEST, TESTCYCL, CYCLE
WHERE CY_CYCLE_ID = TC_CYCLE_ID
AND   TS_TEST_ID = TC_TEST_ID
AND CY_CYCLE_ID IN (cycleid)

Test-Summary:
SELECT CY_CYCLE,
       TC_STATUS,
       COUNT(TS_NAME)
FROM TEST, TESTCYCL, CYCLE
WHERE CY_CYCLE_ID = TC_CYCLE_ID
AND   TS_TEST_ID = TC_TEST_ID
AND CY_CYCLE_ID IN (cycleid)
GROUP BY CY_CYCLE, TC_STATUS
ORDER BY CY_CYCLE, TC_STATUS

Run-rate:
SELECT CY_CYCLE,
       TC_ACTUAL_TESTER,
       TC_STATUS,
       LEFT(CONVERT(VARCHAR,TC_EXEC_DATE,20),10),
       COUNT(TS_NAME)
FROM TEST, TESTCYCL, CYCLE
WHERE CY_CYCLE_ID = TC_CYCLE_ID
AND   TS_TEST_ID = TC_TEST_ID
AND CY_CYCLE_ID IN (cycleid)
GROUP BY CY_CYCLE, TC_ACTUAL_TESTER, TC_STATUS, TC_EXEC_DATE
ORDER BY CY_CYCLE, TC_ACTUAL_TESTER, TC_STATUS, TC_EXEC_DATE
Bottom-Line:
SELECT TC_STATUS,
       COUNT(TS_NAME)
FROM TEST, TESTCYCL, CYCLE
WHERE CY_CYCLE_ID = TC_CYCLE_ID
AND   TS_TEST_ID = TC_TEST_ID
AND CY_CYCLE_ID IN (cycleid)
GROUP BY TC_STATUS
ORDER BY TC_STATUS
Defects:
SELECT BUG.BG_BUG_ID AS "Defect ID",
BUG.BG_USER_03 as "Application",
BUG.BG_SUMMARY AS "Summary",
BUG.BG_DETECTED_BY AS "Detected by",
LEFT(CONVERT(VARCHAR,BUG.BG_DETECTION_DATE,20),10) AS "Detected on",
BUG.BG_RESPONSIBLE AS "Assigned To",
BUG.BG_SEVERITY AS "Severity",
BUG.BG_PRIORITY AS "Priority",
BUG.BG_STATUS AS "Status",
BUG.BG_USER_01 AS "Test Environment",
BUG.BG_USER_02 AS "Test Phase",
BUG.BG_USER_09 AS "Root Cause"
FROM BUG
WHERE BUG.BG_DETECTED_IN_RCYC = 0028
/*AND BUG.BG_USER_01 = 'SIT'*/
AND BUG.BG_USER_02 = 'SIT'
ORDER BY BUG.BG_BUG_ID

Comments

Post a Comment

Popular posts from this blog

Terminal Emulation – QTP Automation Testing

Terminal Emulation – QTP Automation Testing Topics to be covered 1. Basic understanding of the terminal emulator 2. Emulation terminology 3. Configuring the QTP to work with TE application 4. Automation testing methodology Basics of Emulator • Duplicates the functions of one system using a different system, so that second system behaves like a first system. • Computer simulation Example: AS400 and mainframes is a dark green color screen AS400 is introduced in the year of 1988 by IBM, formally renamed as IBM iseries but still called as AS400 is mid range server for the small business and large enterprises. It will work good within distributed network and web based applications for execution it uses OS400 ie operating systems. TN5250 Terminal emulation protocol IBM owned iseries access by TN5250 with WRQ’s reflection, humming bird’s host explorer, Cybele software’s Z scope Express 5250. AS400 is also a Mainframe which are used for large organizations, for critical applic
Read more

Testing Topics

TESTING: ·          White box testing: It requires knowledge of internal program design and coding  It is usually done be the developers to test the programmers ·          Black box testing: Testing system functionality as per the requirements System Testing: System Testing tests all components and modules that are new, changed, affected by a change, or needed to form the complete application. The system test may require involvement of other systems but this should be minimized as much as possible to reduce the risk of externally-induced problems. Testing the interaction with other parts of the complete system comes in Integration Testing. The emphasis in system testing is validating and verifying the functional design specification and seeing how all the modules work together. For example, the system test for a new web interface that collects user input for addition to a database doesn’t need to include the database’s ETL application—processing can stop when the data is moved to the
Read more