This is a draft outline for collaboration on the design of a Pricefx QA test plan framework.

QA Test Plan High-Level

Identification of high-level descriptions for QA plan.

• Definition of Quality (added value)

• QA Vision statement

• QA Scope

  • Formalization of standards

  • Data Migration processing:

    • Data Requirements (BA, Data Readiness Mgr)

    • Data Quality (IE)

    • Transform Process (IE)

    • CI, SI and custom Dashboards (SA, CE)

  • Operational processing:

    • Business Requirements (BA)

      • Operation code (logic)

      • Operational data

      • System integration

      • Reporting

    • Test cases:

      • Black box

      • White box

        • Functional flow (design patterns)

        • View patterns (UI/UX)

        • Model patterns (database access)

        • Controller patterns (business logic)

      • Grey box

  • Project QA compliance

    • Test Plan + test cases

Data Test Plan (Logical to Physical Mapping)

• Data Ownership

  • Data Model Entities

  • Source systems

  • Data Stewardships

• Mappings:

  • Original source

  • Transformations

  • Target

• Business Rules

  • Dates - date + timestamp

  • Unique sequential keys (auto generated)

  • Address - fuzzy logic

• Data Migration QA

  • Data validation

  • High level metric

  • Peer Review standards

    • Augment test plan

    • Test case(s)

    • Expected result

    • Matching to business rules

Logics Test Plan (Pricing Logics))

• User Story

  • Feature (JIRA ticket)

  • Acceptance Criteria

  • Owner

• Mappings:

  • Feature dependencies

  • Transformations

  • Target

Peer Reviews

• Peer Reviews

  • Data transform

    • Test Case(s) + augment Test plan

    • Validation rules

    • Updates to the Metadata repository

      • Source

      • Target

      • Transformation logic

  • Pricing Logic

    • Test Case(s) + augment Test plan

      • Perfect path (Pass or Green)

      • Imperfect path (Fail or Yellow)

      • Illogical path (Reject or Red)

    • Acceptance rules

  • BA and BRD

    • Augment Test Plan

    • Identify test cases

    • Appendix to BRD

  • Test Plan and test cases

    • Mapped to ER model

    • Testing Entities

Details; Test Cases, Compliance and Risk

• Compliance

  • Recovery

  • Stress test

  • Performance

  • Security

  • Functional

  • Usability

• Overall Risk Analysis

  • Analyze risk of priority attributes

  • Provide metric measurement

    • Matrix

    • Weighting factors

• Scheduling

  • Updates for regression testing

  • Nightly (high level)

  • Monthly (More granular)

  • Qtrly (Extensive)

• Test Cases

  • Mapped to Entities and relationships

  • Types of Test cases

    • Standard

    • Customized

  • Expected outcome -

    • Benchmarks

    • Outliers

• Minimal compliance

  • Functional

  • Usability

• Categorization

  • Black-box

    • Roles: QA Team

    • Functional

    • Regression

    • Usability

  • White-box

    • Roles

      • Developer-source code

      • Solution Architect-Conceptual Design

      • IE-Data normalization and standards

    • Functional

    • Regression

Success Metrics

• Key Success metrics

  • Number of test cases

  • Number of test plans

  • Overall passed/failed

  • Tracking data quality errors-tracking (magnitude)

• Defect management process

  • Define defect-via test case

  • Pinpoint area of inspection

  • Complete Ticket

  • Propose resolution

  • Timetable via backlog