Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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

  • No labels