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

Write Unittests for lib/widgets/organization_search_list.dart #2612

Closed
palisadoes opened this issue Oct 27, 2024 · 5 comments
Closed

Write Unittests for lib/widgets/organization_search_list.dart #2612

palisadoes opened this issue Oct 27, 2024 · 5 comments
Labels
feature request good first issue Good for newcomers test Testing application

Comments

@palisadoes
Copy link
Contributor

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

PR Acceptance Criteria

  1. When complete this file must show 100% coverage when merged into the code base.
  2. The current code coverage for the file can be found here
  3. CodeRabbit must approve all your changes to the test file(s) and the file(s) under test
  4. The PR will show a report for the code coverage for the file you have added. You can use that as a guide
  5. No functionality must be removed to achieve this goal
  6. All tests must be valid and truly test the code base

Potential internship candidates

Please read this if you are planning to apply for a Palisadoes Foundation internship

@github-actions github-actions bot added test Testing application unapproved Unapproved, needs to be triaged labels Oct 27, 2024
@palisadoes palisadoes added the good first issue Good for newcomers label Oct 27, 2024
@rohansen856
Copy link

@palisadoes i would like to work on this issue. i will create the unittests in test/widget_tests/organization_search_list_test.dart. please assign me.

@palisadoes palisadoes removed the unapproved Unapproved, needs to be triaged label Nov 10, 2024
@palisadoes
Copy link
Contributor Author

During the week of November 11, 2024 we will start a code freeze on the develop branches in Talawa, Talawa Admin and Talawa-API.

We have completed a project to convert the Talawa-API backend to use PostgreSQL. Work will then begin with us merging code in the develop branches to a new develop-postrgres branch in each repository.

Planning activities for this will be managed in our #talawa-projects slack channel. A GitHub project will be created to track specially labeled issues. We completed a similar exercise last year using a similar methodology.

Starting November 12, California time no new PRs will be accepted against the develop branch. They must be applied to the develop-postrgres branch.

There are some GSoC project features that will need to be merged into develop. These will be the only exceptions.

This activity and the post GSoC 2024 start date was announced in our #general Slack channel last month as a pinned post.

Copy link

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.

@github-actions github-actions bot added the no-issue-activity No issue activity label Nov 21, 2024
@palisadoes
Copy link
Contributor Author

unassigning. inactivity

@github-actions github-actions bot removed the no-issue-activity No issue activity label Nov 24, 2024
@Dante291
Copy link
Contributor

Closing this, Its resolved in this #2646

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request good first issue Good for newcomers test Testing application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants