Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[$250] Add unit tests for approval chain / next approver logic to handle correct optimistic next approver #55003

Open
Beamanator opened this issue Jan 9, 2025 · 7 comments
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 External Added to denote the issue can be worked on by a contributor

Comments

@Beamanator
Copy link
Contributor

Beamanator commented Jan 9, 2025

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!


Goal of issue:

We agreed here and here that it would be great to write unit tests for this project, but we didn't want to hold the project on writing tests b/c it was a pretty complex change that had already gone on for a while.

So in this issue, we will write some tests!! Specifically:

  1. We should create a unit test for getSubmitToAccountID to cover the correct submitsTo.
  2. We should create a unit test for getApprovalChain to cover the correct list order approval chain.

Before the PR is created, let's also check if there's other utils functions that should have unit tests written for them, specifically related to

  1. Advanced & basic & no approvals
  2. Rule approvers (when some exist vs none exist)
  3. Control vs Collect policies

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021877327432534526910
  • Upwork Job ID: 1877327432534526910
  • Last Price Increase: 2025-01-09
  • Automatic offers:
    • nkdengineer | Contributor | 105623817
Issue OwnerCurrent Issue Owner: @eh2077
@Beamanator Beamanator added External Added to denote the issue can be worked on by a contributor Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels Jan 9, 2025
@Beamanator Beamanator self-assigned this Jan 9, 2025
@melvin-bot melvin-bot bot changed the title Add unit tests for approval chain / next approver logic to handle correct optimistic next approver [$250] Add unit tests for approval chain / next approver logic to handle correct optimistic next approver Jan 9, 2025
Copy link

melvin-bot bot commented Jan 9, 2025

Job added to Upwork: https://www.upwork.com/jobs/~021877327432534526910

@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Jan 9, 2025
Copy link

melvin-bot bot commented Jan 9, 2025

Triggered auto assignment to @anmurali (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

@Beamanator Beamanator moved this to Bugs and Follow Up Issues in [#whatsnext] #expense Jan 9, 2025
Copy link

melvin-bot bot commented Jan 9, 2025

Triggered auto assignment to Contributor-plus team member for initial proposal review - @eh2077 (External)

@Beamanator
Copy link
Contributor Author

@nkdengineer is planning to work on this one

@nkdengineer
Copy link
Contributor

@Beamanator I'm here.

@Beamanator
Copy link
Contributor Author

yooo

Copy link

melvin-bot bot commented Jan 9, 2025

📣 @nkdengineer 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Keep in mind: Code of Conduct | Contributing 📖

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 External Added to denote the issue can be worked on by a contributor
Projects
Status: Bugs and Follow Up Issues
Development

No branches or pull requests

4 participants