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

Added splash_screen_test #2372

Closed
wants to merge 2 commits into from
Closed

Added splash_screen_test #2372

wants to merge 2 commits into from

Conversation

Sandesh-03
Copy link
Contributor

What kind of change does this PR introduce?

Unit Test

Issue Number:

Fixes #2145

Did you add tests for your changes?

Yes

Snapshots/Videos:

If relevant, did you update the documentation?

Summary

I wanted to get familiar with testing in Flutter. It was a good opportunity.

Does this PR introduce a breaking change?

No

Other information

Have you read the contributing guide?

Yes

Copy link

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if either of these two conditions occur:

  1. The overall code coverage drops below the target threshold of the repository
  2. Any file in the pull request has code coverage levels below the repository threshold

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

Other

🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Congratulations on making your first PR! 🎊 If you haven't already, check out our Contributing Guidelines and PR Reporting Guidelines to ensure that you are following our guidelines for contributing and creating PR.

@dhanagopu
Copy link

Can you review this PR ? @AdityaBirangal @anwersayeed

@Cioppolo14 Cioppolo14 removed the request for review from AdityaBirangal February 12, 2024 23:52
@Dante291
Copy link
Contributor

@Sandesh-03 remove this file from the codebase as this will be duplicate then.

@Cioppolo14 Cioppolo14 removed the request for review from anwersayeed February 13, 2024 01:03
@Cioppolo14
Copy link
Contributor

@Sandesh-03 Please fix the failing tests.

@palisadoes
Copy link
Contributor

  1. This has to be closed. You have moved the location of the original test file which is not in keeping with the existing structure of the testing regimen.
  2. Make your changes to the original file and resubmit

@palisadoes palisadoes closed this Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Write tests for lib/splash_screen.dart
5 participants