1. FAT : Factory Acceptance Testing: Third party products or customized products which needs to be deployed in the client location before integrating with other applications.
Needs to be validated by the business team, based on their confirmation moved to system testing which will be deployed into the client network.
2. VPT: Volume and Performance Testing: Performance Testing is also called as VPT
3. IVT: Implementation Validation Testing
4. SAT: Service Acceptance Testing: Service team ie Support teams (Integration, Application, Colloboration, Database) will validate the deployment procedure.
5. DOT: Deployment Option Testing: Both old and new software versions of the application should work. 
As per the process, deploy the new code and testing will continue once it is done then support team will reverse the new code to old code ie production code.
This code is tested by the testing team.
Note: Similar to IVT but it is not the same

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,        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_
Read more

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