Posts

Showing posts from 2015

Challenges while executing the test cases for large project

Defects are in Closed status but the test scripts in either Not Completed or Failed or Blocked Status. Based on the conversation with Program Director regarding this, we have followed this method to get more productivity Identify the defects which are closed and find the linked test scripts. Moved those to No Run status by updating the comment section in the test plan>>Run suite. Identified the test scripts which are in the Not completed status for more than two or three days Check the test steps status and if there is an update on those ie more than 50% of the test steps has been executed in that case need to check with the concerned tester for further update. Else move the test script to no run status. Possibility of no action on the test scripts due to concern tester is moved out of the portfolio or left the company or not feeling well or any emergency Defect is in "closed" status, so the test script is moved to "No Run" status t

Analysis on Execution plan

Daily Status Report update. 1.         Who are all stakeholders 2.         Which stakeholder needs what data 3.         Collect the information from the all stakeholder interested on 4.         Create a template and share with the stakeholders to get the signoff. 5.         If there is a need to improve or change in the reporting style, need a confirmation from the Business/TCS Managers. Daily status report : Information Interested on : Ideal Scenario: All test cases/scripts are passed and all defects to be closed before the EOD of test execution cycle. 1.         How much work is completed/how much is pending 2.         Whether we can complete the task in time 3.         What is the percentage of the pass test scripts when compared to the base line plan 4.         Execution plan vs Actual Plan ie Baseline plan VS Forecast plan(have we complete the execution as per the plan, else how much is pending + how much needs to be completed tomorrow= is our target to c

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_

HP ALM-QC Daily report extraction

SIT Test Lab will extract the Test Set, test case name, executed on, Executed by and it status. 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 (Cycleids) High level summary of the metrics 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 (cycleids) GROUP BY CY_CYCLE, TC_STATUS ORDER BY CY_CYCLE, TC_STATUS SIT Execution Rate/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

HP QC-ALM Reporting Queries

Duplicate_TestScripts_TestLab select rcyc_id as cycle_id, cycle_name, cy_cycle_id as test_set_id, cy_cycle as test_set_name, test_id, ts_name from testcycl t join cycle on cy_cycle_id = tc_cycle_id join ( select rcyc_id, rcyc_name as cycle_name, tc_test_id as test_id from release_cycles join testcycl on tc_assign_rcyc = rcyc_id -- where rcyc_name = 'MY CYCLE NAME' group by rcyc_id, rcyc_name, tc_assign_rcyc, tc_test_id having count(tc_test_id) > 1 ) multi on test_id = t.tc_test_id and tc_assign_rcyc = rcyc_id join test on ts_test_id = t.tc_test_id order by 2, 6, 5, 4 Number of Test Steps Count for not passed status. SELECT CY_CYCLE AS "Test Set",        TS_NAME AS "Test Script Name",        TS_STEPS as "Test Steps", /*Test.Steps*/        TC_ACTUAL_TESTER AS "Tester",        TC_STATUS AS "Execution Status", LEFT(CONVERT(VARCHAR,TC_EXEC_DATE,20),10)  AS "Execution Date" FROM TEST, TESTCYCL,

Don't run the project, so it is assigned to you. Follow the standard, process to complete.

Project Manager gave the project plan at the end stage of the project. With the given dates, Testing team has to build the test execution plan. I saw lot of problems and wastage of the effort in doing the testing. Because IT/SIT/UAT all these environments doesn't have the valid test data to test. PPE you will have to do the testing in full fledged where there is a limitation of space. So we will be testing the sample test data. Based on the given plan, Testing team has to execute parallel in all three env. Lot of rework for the development and testing team.(Wastage of time) Note: 1. If you are not assigned to the project. Don't work on that project, simply screw the other person work. 2. If you don't have knowledge on testing/development/Build works, Shut your mouth.

Appraisal Talk

Appraisal Talk First Managers will start with three points stating , 1.  how long working with current account (They should know, account has project which needs a resources for that position we got filled) 2. Do you have any complaints from the clients/ managers regarding the work. As you all know, Managers like his empire. If you do great things he will not be able to see those achievements because it is covered his circle or friends or relatives or disciples etc.. later you will come...So you last this appraisal. 3. Scope of work Manager explains in your last project you may be scientist but your current position is test manager. Any manager should understand, he crossed the same appraisal discussion when he is young or in hos carrier. Scientist always a scientist whatever the opportunity is whether it is small project or big project or scope of the work. Scientist always be a creative. My grandma says "Lion is king of animals whether it is Forest, Zoo or Circus)

About Test Data

Test data is needed for Testing an application/product. What are the different types of test data? There are four different types of test data 1. Synthetic test data or some call as Artificial test data: Which is created by the testing team with minimal knowledge on Business domain and may not able to replicate as production data. Eg: SSN number and account number: Which is secured numbers which testing team know the size of the SSN number so team provides 9 digits to test it. Similarly the account number based on the bank size of the account number will be defined. With the help of Business analyst team create the account number but the same account number will be used n number of test cases. 2. Pre-production test data: Where the data is extracted from the Production and it will be processed and pushed the testing env for testing the application. This test data is very useful and provides clear testing of an application. Where we can get the test data? Who can provide the