Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
B
Business Systems Analysts
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 35
    • Issues 35
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.com
    • Business Technology
    • Enterprise Applications
  • Business Systems Analysts
  • Business Systems Analysts
  • Issues
  • #53

Closed
Open
Opened Dec 19, 2020 by Barbara Roncato@broncatoOwner6 of 6 tasks completed6/6 tasks

Xactly CEA: Pre-UAT Preparation

Pre-UAT Preparation checklist

  • Finance team to attend CEA Walkthrough.
    • Demo performed on the 25th of Jan. Recording here (reach out to @broncato for the password if needed).
  • Finance team to create UAT test cases.
    • Test cases defined here.
  • @broncato Assign UAT test cases to the testers.
  • @broncato Have production and/or sandbox data ready for integration testing.
  • @broncato Verify system access for all testers (Incent, CEA, JIRA for ticket tracking).
  • @broncato UAT logistics (who, where, when, etc).
    • UAT will be tracked in this issue.

General Guidance

  1. If you find an error, report the issue in JIRA and assign it to Bill Tang; they will reassign if necessary.
    • Include AT MINIMUM the name of the Object with corresponding Model, Portfolio that you were testing, the period, the result you were expecting vs the result you saw.
    • The more detail you provide reporting an issue, the quicker it will be resolved (e.g. "US Model for Deferred Commission Expenses in Jan-2018 shows capitalization of $1,000,000, but I expect $500,000" will be resolved in 5 minutes, whereas "the US Model looks wrong" will take 6 hours).
  2. Once you log the issue MOVE ON to the next test case that is not dependent on the answer of the case that failed.
  3. Once the issue is resolved, it will be reassigned to the person who opened the issue with a status of "Retest", please retest the issue as quickly as possible and either close it as "Resolved" or reassign it back to the CC if you still see an issue, with a note about what the current issue is.
  4. If the issue you report is determined to be a new requirement or change to the documented requirements in the FRD, those issues will be put in the parking lot and reviewed after UAT is complete.
  5. Run multiple periods of data, AT MINIMUM 1 full quarter.
  6. Test data sets with production e.g. commission counts and values via integration (integration).
  7. Be sure to process a full monthly cycle, including closing the period and reviewing adjustments.
  8. Use end user reports and validation reports to validate results.
  9. Review edge cases and outliers (negative results, claw-backs, adjustments, churns etc).
Edited Jan 26, 2021 by Barbara Roncato
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
Jan 25, 2021
Due date
Jan 25, 2021
Reference: gitlab-com/business-ops/enterprise-apps/bsa/business-systems-analysts#53