Best Practices in testing


·         Determine the Focus of the Test Before beginning.
·         Create Test Scenarios – Follow the Application functionality when creating
·         Scenarios should have multiple test cases tied to each.
·         Positive Test Cases – Acceptable Input Data  - Expected to Work
·         Negative Test Cases – Unacceptable Input Data  - Expected NOT to Work
·         Creative Brainstorming Test Cases  - Helps detect  unexpected results
·         Consider Risk Factors – Increase number of test cases for volatile areas of the systems, complex code, newly created code.
·         Number of Test Cases – Average is 2 to 3 per function ( for Low to Medium Risk Factors)

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

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,        L...
Read more

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...
Read more