irreproducible bugs become highly reproducible right
play

Irreproducible bugs become highly reproducible right after delivery - PowerPoint PPT Presentation

Irreproducible bugs become highly reproducible right after delivery to the customer Michael Stahls derivative to Murphys Law 2 Markets Release 1.19 Market Participant Testing Kick-Off 3 Agenda The Why The What


  1. “Irreproducible bugs become highly reproducible right after delivery to the customer” – Michael Stahl’s derivative to Murphy’s Law 2

  2. Markets Release 1.19 Market Participant Testing Kick-Off 3

  3. Agenda The Why • The What • The Who • The When • The Where • The How • 4

  4. The Why • Allow Market Participants to Become Familiar with the Updates and Changes Contained in Release prior to Production • Ensure Changes are Functioning as Designed and Requested • Ensure the Quality of the Software 5

  5. The What… Member Impacting Issues • Issue 3356: Allow users to use the Virtual Bids/Offers post API operations to delete Virtual Bids or Offers • Issue 3975: Improve data structure for Overrides in Markets API and Notification to assist with data parsing • Issue 4559: Include Endpoint Address on Markets UI Transaction Log page and associated API operation • Issue 4560: Add unique ID to Markets XML notifications • Issue 1818: Identify MP Self-Commits and Market Commits on Markets UI Commitment page and corresponding API operation 6

  6. …The What Continued… Member Facing Issues • Issue 3035: Display timestamp of override entry on Market UI • Issue 1301: Allow User Preferences to Saved in Markets UI • Issue 1302: Move Messages and Filtering Options to Top of Display on Markets UI • Issue 3480: Remove Post Reserve Status Set operation from the Reserve WSDL • Issue 4779: Set Mitigation Detail Element to Unbounded in Commitment History Operation 7

  7. …The What Concluded Member Facing Issue • Issue 4513: Overrides that span multiple days should be returned in the Markets Energy Web Service API • Testing of the issue is optional and test cases are not provided– please make a request via RMS if you would like to test this item 8

  8. The Who Market Participants • Execute all test cases applicable to entity • Turn in results spreadsheet EOB Fridays via RMS • Complete Structured Testing by Friday, September 30 • Complete Unstructured Testing by Friday, October 14 • Contact SPP with all questions or for assistance via RMS (Quick Pick: Project Inquires; Sub-Type = Markets Release 1.19) 9

  9. The Who SPP Staff • Support MP Structured Testing • Respond to Market Participant RMS tickets in timely manner • Communicate any changes and/or updates regarding testing in timely manner • Post Testing Scorecard weekly 10

  10. The When • September 1 – October 14: Markets 1.19 MP Testing Period  Structured Testing: September 1 – September 30  Unstructured Testing: October 1 – October 14 • September 22: Testing Status Call • November 8: Markets Release 1.19 Migrates to Production 11

  11. The Where Member Testing Environment • Supported Monday – Friday, 8:00am to 5:00pm CPT • Utilizes Gas Day Timeline 12

  12. The How • Markets Release 1.19 Member Impacting Project Overview • Markets Release 1.19 Test Cases • Markets Release 1.19 Testing Scorecard • MOS 1.19 API Specifications 13

  13. Questions  Contact SPP via the Request Management System  Quick Pick: Project Inquires  Sub-Type: Markets Release 1.19 14

Recommend


More recommend