Alliance2011 goldcoast Farid


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Process Testing
  • Here is a quick example
  • Alliance2011 goldcoast Farid

    1. 1. Testing for 20 months – how costeffective is that?Session #3102801 December, 2011Farid VaswaniUniversity of AucklandTwitter: @FVaswani
    2. 2. Experience o 12 years IT experience in Development & Testing o Conference Speaker o Techie / Grumpy / Unsatisfied TesterResponsibilities • Testing Manager, University of Auckland o Team of 8 - 20 Testers and Test Engineers • Associate Board Member, ANZ Testing Board o Enhancing Career Opportunities for Testing Professionals
    3. 3. o 40,000 studentso 5,000 staffo 8 Facultieso 2 large-scale research instituteso 4 main campuses
    4. 4. o PeopleSoft CSo PeopleSoft HRo PeopleSoft FINo Databaseso WebLogic Servero RightNow (CRM)
    5. 5. CCv7.6 (nDEVA) JAVA Batch Processes AFAEPRv1 (Portal)
    6. 6. CS v9 WLI DSSEPR AFAv2 v2
    7. 7. o Oracle supporto SOA architectureo Real-time updateso Identity & Access Managemento Usabilityo Hardware virtualisationo Performanceo Students o
    8. 8. Project FOCUSFocus On Changing University Services
    9. 9. o Budget: eight-figure $ amounto 63 business process, to be rewritteno 500+ staff affectedo 40,000+ student recordso 400,000 rows in one of the tableso 10+ years of data to be migratedo Project team size: 50+ FTEo + UAT testers
    10. 10. It’s just anotherPeopleSoft upgradeproject
    11. 11. Programme Manager Process Manager Data Conversion Manager Development Manager Integration Lead EA Lead Security Lead Testing Manager
    12. 12. 1. Testing Types2. Testing Responsibilities3. Test Team4. Testing Approach5. Testing Schedule6. Testing Tools7. Test Reporting
    13. 13. o Data Conversion Testingo Process Testingo Enhancement Testingo Integration Testingo Performance Testingo Security Testingo Usabilityo Compatibilityo User Acceptance Testingo Go-live
    14. 14. Process Testing Manager DSS Manager Manager Process Team Test Team Reporting Team (15) (6) (4) DC Tester Security Tester (2)Data Conversion Security Manager Manager
    15. 15. Process Testing Manager DSS Manager Manager • Functional Process Team • Integration Reporting Team (12) • Performance (5) • Automation • Compatibility • Security Scans DC Tester Security TesterData Conversion Security Manager Manager
    16. 16. Tip #1:Way in to otherteams’ time is through their managers.
    17. 17. Data Conversion TestingCC v7.6 International -> CS v9.0 Asia-Pac o CC v7.6 -> CC v8.0 -> CS v9.0 o Vanilla upgraded by Oracle lab o Customisations, converted (implemented) in-house
    18. 18. Data Conversion TestingTesting o Field mappings o Field counts o Record counts o GUI testing o EPR-CS9 reconciliation
    19. 19. Data Conversion Testing Tip #2:Data Conversion testers are good functional testers during their down time.
    20. 20. Data Conversion Testing Tip #3: Never underestimate the value of manual GUI checking after DC.
    21. 21. Process Testing10 Mega processes, 63 sub-processes o Admissions o Enrolment o Manage Campus Community o Financial Services o Financial Support o Teach Learn Evaluate o Transition Student o Advisement o Self Service o Reporting
    22. 22. Process TestingTesting o 6 Process Leads + 9 team members o Written Test Cases o Exploratory Scenarios o Mostly positive testing for staff based functionality
    23. 23. Process Testing Tip #4: Attend Process workshops; all of them, if possible.
    24. 24. Enhancement TestingScope + Testing o 54 enhancements o PeopleSoft only o Split between QA & Process team o Written Test Cases o Exploratory Scenarios o Some negative testing included
    25. 25. Enhancement Testing Tip #5: Good to keep a tap on business testers when writing test scripts.
    26. 26. Integration Testing*1* Interfaces o WLI o Data Extracts o Third party o Studylink (student loans) o National Student Index o Payment Gateway o Technical Testers responsible for these
    27. 27. Integration Testing*2* Process Integration o Student lifecycle o Various start & end points o Multiple processes o Multiple systems
    28. 28. Integration Testing*2* Process Integration o Scenario 1 (e.g.) o Admission > Enrolment > Fees > Exam > Completion > Graduation o Domestic student o NCEA o NSI o Undergrad o Student loan o 1st year student
    29. 29. Integration Testing*2* Process Integration o Scenario 4 (e.g.) o Admission > Enrolment > Fees > Visa Processing o International student o Post grad o 120 points o Paying full fees
    30. 30. Integration Testing*2* Process Integration o 7 scenarios o 45 (out of 63) sub-processes o 10 external systems o 240 transitions o One person responsible for these
    31. 31. Integration Testing Tip #6: Book some extra time slots for testing with external-party, in advance.
    32. 32. Performance TestingChallenge CS9 AFA WLI • Staff • Student • World using it • Batch • EOI • Relatively new • Transactions • EPR • Real-time • Reports • Self Service Infrastructure
    33. 33. Performance TestingTesting: Hybrid approach o 6 batch processes: manual o eg: Generate Invoice, Advisement, Transcript o Student Self-Service: automated o Staff transactions o Manual and automated data generation scripts o 14 reports, manual o AFA, automated o 9 WLI interfaces, scripted
    34. 34. Performance Testing Tip #7: Pre-Prod is NOT Test
    35. 35. SecurityTesting o Application Penetration Tests o User roles o Staff vs Students o Positive & Negative o Infrastructure Scan o Security certificates o Split URLs o o
    36. 36. Security Tip #8:Make an effort to understand security-speak
    37. 37. UsabilityUsability Testing
    38. 38. UsabilityUsability o Review… o Personas… o Wire-frames… o Mock screens… o Real people… o Iterate ---^
    39. 39. Usability Tip #9: Consult SteveAlexander
    40. 40. Compatibility Testing We Tested ALL Users want We supportOraclesupports
    41. 41. User Acceptance TestingTesting o Subject Matter Experts… o …supported by Process Leads o 3 cycles… o …on rotation basis o MS-Word templates
    42. 42. Security Tip #10:SMEs are busy. Taketheir BAU schedule into consideration when planning.
    43. 43. Security Tip #11:UAT is not a Training opportunity.
    44. 44. Go-live TestingTesting o Business critical scenarios o Integration scenarios o Reports o Self-Service o People: QA, Process, SMEs o Google Docs o allowed simultaneous editing
    45. 45. Go-Live Testing Tip #12: Include SMEs.
    46. 46. o 4 test cycles o Process & SMEs o Priority based o Partial processeso Enhancements (non-PS) o Agile, continuous testingo Non-functional o Performance – last 3-4 months o Security – 3 scans
    47. 47. o HP Quality Centre o Test case managemento Jmeter o Performanceo soapUI o Web – services o Functional & loado HermesJMS o WLI queueso AppScano MS-Word, MS-Excelo Google Docso Confluence wikio Jira
    48. 48. Defects Raised per Week250 Low200150 Medium100 High 50 0 Week Ending
    49. 49. Defect Status 2500 2000 Opened 1500 Cumulative Total 1000 Closed Cumulative 500 Nett Open 0 Reopened Week Ending 2500 Defects Forecast Actual 2000 ExpectedCumulative Defects 1500 1000 500 0 -500 Week Ending
    50. 50. Tip #0:Start Early. Test Early. Deliver on time.
    51. 51. Video:
    52. 52. Farid Vaswani Testing Manager ITS, Group Applications University of Auckland E-mail: Twitter: @FVaswani
    53. 53. This presentation and all Alliance Down Under 2011 presentations are available for download from the Conference site at www. heug.orgPresentations from previous meetings are also available