dominos-workflow.md

This is a rough project flow we use when taking on new tasks;

1. Build your UI elements (Storybook) or adjustments based on any mocks in your card.
2. Integrate elements into the application, making it a dynamic component.
3. Create tests and run localized testing on all files you've touched yarn test:all --watch ~/path/to/file --coverage false
4. Turn coverage on and address missing lines in your tests yarn test:all --watch ~/path/to/file --coverage. You might need to add --updateSnapshot to your local tests if you've modified the outputted component and receive snapshot errors.

Alternate back and forth between addressing coverage and fixing tests until all local tests pass.5. Once everything passes locally and coverage is high, run a unit test on the entire project

yarn go
  > Run Tests
    > Run Unit Tests
      > Run all Tests
      - Watch = No
      - Update Snapshots = No

6. If the full project tests pass, you're ready to run linting

yarn go
  > Run Code Linting

Do this before final commits as this will update allot of code styling and annoying things like alphabetic imports.

7. Commit your final changes onto your branch.
8. Push your branch with git push.

Navigate to Azure DevOps > Repos > Branches

9. Select your branch, open a "Pull Request", label with the title of your card and link work items, then publish.
10. Once the build has succeeded, post a link to your PR on Phoenix Engineering asking for "dev approval".
11. Notify your assigned team QA that your project is ready for testing.