Session ID: BTOT-TU-1800/1<br />Twitter hashtag #HPSWU<br />
How to use QTP and Quality Center for daily automated regression test Type: BTO Applications<br />Speaker Name: Test Manag...
Agenda<br /><ul><li>ATP – the company and the test organisation
System landscape and regression test
Requirements for our testing tools and automated test setup
The setup for automated testing
Communication with relevant stakeholders
Daily mail with graphs
Daily follow-up on the nightly runs
Progress on developing automated tests
How did we get there? Prerequisites for our autotest setup</li></li></ul><li>Brief presentation of ATP:  Company tasks<br ...
Test Organization<br />The test resources<br />3 Head of Test<br />6 Test Managers (RTM, TI and TM)<br />9 Test coordinato...
Test Organization - automatisation<br />Centralized automation team<br />Building principles and guidelines<br />Coordinat...
SAP client<br />Guitalis<br />Doc./Papyrus/WAS<br />Kerne/.NET/DB2<br />SAP<br />Masterdata/WAS<br />WFM/WAS<br />Broker /...
Service requests
Batch runs</li></li></ul><li>Test of new functionality<br />Regression test of previously delivered functionality<br />Rel...
Requirements for our Testing Tools<br />We want to use our current tools Quality Center and QTP<br />We have to be able to...
Automation focus areas<br /><ul><li>Services
Alive
Functional
Upcoming SlideShare
Loading in...5
×

How to use QTP and Quality Center for daily automated regression test Type: BTO Applications

10,752

Published on

An overview of how to use QTP and Quality Center for daily automated regression test Type: BTO Applications, using a case study of ATP

1 Comment
1 Like
Statistics
Notes
  • sujet interessant
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
10,752
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
83
Comments
1
Likes
1
Embeds 0
No embeds

No notes for slide

How to use QTP and Quality Center for daily automated regression test Type: BTO Applications

  1. 1. Session ID: BTOT-TU-1800/1<br />Twitter hashtag #HPSWU<br />
  2. 2. How to use QTP and Quality Center for daily automated regression test Type: BTO Applications<br />Speaker Name: Test Manager Maja Usbeck Cao <br />and Test Specialist Claus Haslund Andersen<br />Date: 30. november 2010<br />Session ID: BTOT-TU-1800/1<br />
  3. 3. Agenda<br /><ul><li>ATP – the company and the test organisation
  4. 4. System landscape and regression test
  5. 5. Requirements for our testing tools and automated test setup
  6. 6. The setup for automated testing
  7. 7. Communication with relevant stakeholders
  8. 8. Daily mail with graphs
  9. 9. Daily follow-up on the nightly runs
  10. 10. Progress on developing automated tests
  11. 11. How did we get there? Prerequisites for our autotest setup</li></li></ul><li>Brief presentation of ATP: Company tasks<br />Regulated tasks<br />Customers contact with the ATP Group<br />Pension og Security<br />Security<br />Pension<br />Pension Danmark<br />JØP (Unit Link)<br />DA-Barsel<br />ATP<br />SP<br />SUPP<br />LD<br />AER<br />AES<br />FerieKonto<br />LG<br />Barsel.dk<br />Pension(Pension services)<br />Vocational training (internship grants)<br />Maternity(salaries refunding)<br />Occupational disease(Workers’ compensation insurance)<br />Bankruptcy(pay compensation)<br />HolidayHoliday pay)<br />4.4 million Danes come in contact with the ATP Group's products. Total products<br />ensures our customers a basic economic security during and after their working lives.<br />
  12. 12. Test Organization<br />The test resources<br />3 Head of Test<br />6 Test Managers (RTM, TI and TM)<br />9 Test coordinators<br />3 Test specialists (automated test and test data)<br />Up to 4 IT-Testers and students workers (ITU and DTU)<br />23 Test consultants<br />Responsibility area<br />Test in projects and Sustained Engineering<br />Test methods, TDM and test tools (QC, QTP and Loadrunner)<br />
  13. 13. Test Organization - automatisation<br />Centralized automation team<br />Building principles and guidelines<br />Coordination across the organization<br />Upgrade & support of the tool<br />Building regression test <br />Maintenance of automated test<br />Responsibility for the daily runs<br />Sometimes QTP developers are lent to projects for a period of time<br />
  14. 14. SAP client<br />Guitalis<br />Doc./Papyrus/WAS<br />Kerne/.NET/DB2<br />SAP<br />Masterdata/WAS<br />WFM/WAS<br />Broker / Websphere MQ<br />Websphere<br />HTTP<br />Portal 360o<br />Portal<br />ATP Business Platform - Logical overview<br />Execution of:<br /><ul><li>GUI transactions
  15. 15. Service requests
  16. 16. Batch runs</li></li></ul><li>Test of new functionality<br />Regression test of previously delivered functionality<br />Release<br />1<br />2<br />3<br />5<br />4<br />6<br />7<br />Regression test purposes<br />Regression testing aims to test whether any errors occurs in already implemented functionality, when implementing new or changed functionality.The extent of regression test and risk of missing regression test increases in proportion to the implementation of new functionality (see illustration).Missing/incomplete regression test represent a quality risk<br />
  17. 17. Requirements for our Testing Tools<br />We want to use our current tools Quality Center and QTP<br />We have to be able to run our test set on a scheduled basis: Daily, weekly and individual dates<br />Automatic re-running tests that fails the first time (based on percentage of failed tests in a test set)<br />Distribution of loads on x number of machines (so we continuously can expand our setup)<br />Grouping of servers, so test on different releases is possible (Sustained Engineering and release)<br />Troubleshooting - current screenshots of the machines and embedded error detection in scripts<br />We need to know the expected execution time for a test set (Crucial when time is short eg. emergencies)<br />Don’t think: What you can get – Think : What you want!<br />
  18. 18. Automation focus areas<br /><ul><li>Services
  19. 19. Alive
  20. 20. Functional
  21. 21. Batch runs (via gui)
  22. 22. Start of batch run
  23. 23. Check result
  24. 24. System testing
  25. 25. Deep functional
  26. 26. Testdata
  27. 27. Creation of data
  28. 28. Deleting data
  29. 29. Environments
  30. 30. Component
  31. 31. Integration
  32. 32. Pilot</li></li></ul><li>Doc./Papyrus/WAS<br />Masterdata/WAS<br />Kerne/.NET/DB2<br />SAP<br />WFM/WAS<br />Broker / Websphere MQ<br />Websphere<br />HTTP<br />Portal 360o<br />Portal<br />Test of Service requests - solution<br />There are 6 main systems providing services.<br />Application for communication (Broker).<br />The portal using these services.<br />One automated BPT component in Quality Center.<br />QTP<br />QC<br />ATSA<br />
  33. 33. Automation Test environment<br />Automated Test Scheduler Application (ATSA) <br />
  34. 34. What is the ATSA and how does it work?<br />
  35. 35. Daily status on the test execution<br />Daily mail with information on the execution of automated tests<br />
  36. 36. Daily monitoring of test execution<br />The main reason that there are 26 failed tests, time out and changed data.<br />Errors are described in details below (note that you can not compare the numbers directly, as part of the failed setup test cases are not counted as<br />test cases)<br />Portal:<br /> PD: Passed.<br /> DFO: Errors due to environmental instability. There is created POB-action on that.<br /> SUPP: Passed<br />Service requests:<br />Alive test:<br /> ATP: 2 Broker Time out (Defect 16159). <br /> PD: 5 Broker Time out (Defect 16159). <br />Functional:<br /> AER: Passed.<br /> ATP:3 Broker Time out (Defect 16159). <br /> PD:2 fails because of environment setup (service call is send to wrong environment). <br /> 1 Broker Time out (Defect 16159). <br /> SUPP: 1 Broker Time out (Defect 16159). <br />Kernel:<br /> ATP: 2 errors in death batch job because of time out of the stakeholder replication<br /> 3 data / environment errors on K060.<br /> PD: 3 kernel time outs<br /> 5 Data / rounding errors on the letters and H150<br /> 3 fails due to customer agreement does not work (H150). Defect has been created<br /> SUPP: 9 Data / rounding error on the letters and F02 <br /> 4 fails because of data / setup<br />
  37. 37. Number of automated tests over time<br />
  38. 38. Approach on automated test<br /><ul><li>Standard for BPT (content, size and structure)
  39. 39. It is mandatory to use BPT in all regression tests
  40. 40. Education in BPT components (workshops on our customers applications)
  41. 41. Review of the BPT components (both manual and automated)
  42. 42. Code guideline
  43. 43. Code review
  44. 44. Automation team located in the same room (communication)
  45. 45. Data discipline in QC is crucial (data for our graphs)</li></li></ul><li>Test data and change of test environments<br /><ul><li>Test data used for the automated tests must be reserved in all test environments
  46. 46. Solution established for deleting and reload of data in our component test environments
  47. 47. The automated test generates data and cleans up data</li></li></ul><li>How did we get this far<br /><ul><li>Management focus on automation - it has taken a long time to reach this far (maturity)
  48. 48. Visibility on automated testing - we get that by sending out a daily mail with graphs and mark all defects found
  49. 49. We can test a large part of our regression tests automatically in one night and it can be used for bug fixes in production
  50. 50. Over time - lower costs on our regression test
  51. 51. Centralized automation team is crucial for our success
  52. 52. Important to focus on maturity of the company (we are now TMMi level 2 – moving towards level 3)</li></li></ul><li>Continue the conversation with your peers at the HP Software Community hp.com/go/swcommunity<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×