Pre-Shipping

The Pre-Shipping project in OSDU Forum is setup to represent the interest of the consumers, (majorly energy companies and Operators) thereby, solely focusing on performing test validation activities for each Milestone release prior to being released into production for the wider opengroup community.

We follow the published OSDU community milestone release process to validate all changes and updates (new features, functions, bug fixes etc.) for each milestone release of the OSDU Data Platform, ensuring it is appropriately tested before it is being shipped to the Operators or OSDU data platform consumers across the energy industry ecosystem.

We mainly focus on the workflow validations from the operators or business user's perspective while also, adding value by suggesting feature enhancements and raising issue bugs needing to be fixed.

The folder structure on this page has been setup to facilitate the sharing of test validation artifacts from all CSPs (AWS, Azure, IBM, GC and RI) and also, from the QA-Audit testers. Each milestone release will have a folder structure where the underlisted artefacts can be uploaded for Pre-shipping validation testers to commences its validation activities following deployment of the milestone release to the Pre-Shipping environments.

**CSPs - AWS, Azure, IBM, GC and RI ** - these are the following requirements expected to be uploaded in your respective folder under each milestone release area

• JSON Environment Files & URLs/Endpoints
• Authentication Credentials (please email to david.glass@sword-group.com , todaiks@att.net, samiullah.ghousudeen@bp.com & Debasis.Chatterjee@katalystdm.com)
• Postman authentication procedures and clear guide
• CSP's Smoke Test Postman collections covering common R3 Core Services (Ex: Legal, Search, Storage, Ingestion….)
• List of feature changes
• Airflow Console and login information
• Clear instruction about file upload to cloud (required for work-product component validation)
• Test data (TNO, Volve) loaded
• Standard set of Data Reference values populated (including CRS, Units)
• Additional Postman Collections and guide for advanced features (ex: Seismic DDMS, CSV Ingestion etc.)

QA-Audit - these are the following requirements expected to be uploaded in your assigned folder (QA-Artifacts) under each milestone release area

• Test Cases / Test Data
• Test Procedures/Instructions
• Generic Platform Validation Postman Collections (configured/tested for all CSP environments)
• Test Env Workflow Pass %
• Documented workarounds for UAT testing
• Demo Videos (if made available from Developers)

Pre-shipping Validation Testers - please note below for reporting results each milestone release area and;

1. Document your results and update name with this convention

• Mx-CSP-ScopeShortDescription-Firstname

2. Name file using the following naming convention E.g. M23-Azure-AdminUI-Grant; M23-GC-MasterFoRDateConv-Debasis; M23-IBM-WellboreDDMS-Esmira
3. Upload your updated file in the Milestone Result folder (ensure file naming convention in step 2 adhered)

• e.g https://community.opengroup.org/osdu/platform/pre-shipping/-/tree/main/R3-M22/Results

Pre-Shipping Stakeholders