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

Add test coverage for Context classes in frontend #134

Closed
2 of 6 tasks
AnthonyMadia opened this issue Oct 26, 2022 · 1 comment · May be fixed by #148
Closed
2 of 6 tasks

Add test coverage for Context classes in frontend #134

AnthonyMadia opened this issue Oct 26, 2022 · 1 comment · May be fixed by #148
Assignees
Labels
wontfix This will not be worked on

Comments

@AnthonyMadia
Copy link
Contributor

AnthonyMadia commented Oct 26, 2022

This context is being tested within the current unit tests but does not have isolated unit test coverage.

Context:

  • EpochManager
  • Post
  • Prover
  • Queue
  • Unirep
  • User
@AnthonyMadia AnthonyMadia self-assigned this Oct 26, 2022
@AnthonyMadia AnthonyMadia moved this to 🔖 Current sprint in Unirep Social Scrum Oct 26, 2022
@AnthonyMadia AnthonyMadia linked a pull request Nov 2, 2022 that will close this issue
13 tasks
@AnthonyMadia AnthonyMadia changed the title Add test coverage for Context objects in frontend Add test coverage for Context classes in frontend Nov 10, 2022
@AnthonyMadia AnthonyMadia moved this from 🔖 Current sprint to 👀 In review in Unirep Social Scrum Nov 14, 2022
@ChialiT ChialiT added the wontfix This will not be worked on label Mar 2, 2023
@ChialiT
Copy link
Member

ChialiT commented Mar 2, 2023

Won't fix due to sunsetting the project

@ChialiT ChialiT closed this as completed Mar 2, 2023
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in Unirep Social Scrum Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants