-
-
Notifications
You must be signed in to change notification settings - Fork 506
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
Write tests for access_request_screen.dart #2151
Comments
May I take this issue? |
@SatwikMohan Please follow the template while creating a PR and must link the issue associated with the PR so that it closes automatically. |
Sure sir, from now on I will. |
This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue. |
@SatwikMohan You have created more than 5 PRs on this issue and none of them got merged. Are you still working on this, its been more than 2 weeks. |
@noman2002 Sir you told me to fix formatting error 1 week ago from that day today I got time to work on the issue. Sir I am eager to learn and contribute, I am just trying my best since I am new in open source. If you can guide me through some sources so I can improve my PRs as I still want to work on this PR. |
This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue. |
Removing assignment due to no activity and no related pull request |
Please assign me this issue |
The Talawa code base needs to be 100% reliable. This means we need to have 100% unittest code coverage. No functionality must be removed to achieve this goal.
We will need unittests done for all methods, classes and functions found in this file.
Any widgets referenced in this file must also have unittests done
The current code coverage for this file can be found here:
The text was updated successfully, but these errors were encountered: