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

chore: tests cleanup #256

Closed
wants to merge 8 commits into from
Closed

chore: tests cleanup #256

wants to merge 8 commits into from

Conversation

mrehan27
Copy link
Contributor

@mrehan27 mrehan27 commented Sep 15, 2023

Part of Fall 2023 Cleanup

Changes

  • Remove unused tests
  • Refactored unit tests to test directory and instrumented tests to androidTest for better testing experience
  • Removed code for merging sharedTest, tests will now follow normal structure for Android projects
Related PRs (to be merged in sequence)

@mrehan27 mrehan27 self-assigned this Sep 15, 2023
@github-actions
Copy link

github-actions bot commented Sep 15, 2023

Pull request title looks good 👍!

If this pull request gets merged, it will not cause a new release of the software. Example: If this project's latest release version is 1.0.0. If this pull request gets merged in, the next release of this project will be 1.0.0. This pull request is not a breaking change.

All merged pull requests will eventually get deployed. But some types of pull requests will trigger a deployment (such as features and bug fixes) while some pull requests will wait to get deployed until a later time.

This project uses a special format for pull requests titles. Expand this section to learn more (expand by clicking the ᐅ symbol on the left side of this sentence)...

This project uses a special format for pull requests titles. Don't worry, it's easy!

This pull request title should be in this format:

<type>: short description of change being made

If your pull request introduces breaking changes to the code, use this format:

<type>!: short description of breaking change

where <type> is one of the following:

  • feat: - A feature is being added or modified by this pull request. Use this if you made any changes to any of the features of the project.

  • fix: - A bug is being fixed by this pull request. Use this if you made any fixes to bugs in the project.

  • docs: - This pull request is making documentation changes, only.

  • refactor: - A change was made that doesn't fix a bug or add a feature.

  • test: - Adds missing tests or fixes broken tests.

  • style: - Changes that do not effect the code (whitespace, linting, formatting, semi-colons, etc)

  • perf: - Changes improve performance of the code.

  • build: - Changes to the build system (maven, npm, gulp, etc)

  • ci: - Changes to the CI build system (Travis, GitHub Actions, Circle, etc)

  • chore: - Other changes to project that don't modify source code or test files.

  • revert: - Reverts a previous commit that was made.

Examples:

feat: edit profile photo
refactor!: remove deprecated v1 endpoints
build: update npm dependencies
style: run formatter 

Need more examples? Want to learn more about this format? Check out the official docs.

Note: If your pull request does multiple things such as adding a feature and makes changes to the CI server and fixes some bugs then you might want to consider splitting this pull request up into multiple smaller pull requests.

@github-actions
Copy link

github-actions bot commented Sep 15, 2023

Sample app builds 📱

Below you will find the list of the latest versions of the sample apps. It's recommended to always download the latest builds of the sample apps to accurately test the pull request.


  • kotlin_compose: rehan/cleanup-tests-renaming (1694787118)
  • java_layout: rehan/cleanup-tests-renaming (1694787119)

@codecov
Copy link

codecov bot commented Sep 15, 2023

Codecov Report

Merging #256 (abfb8d8) into main (365a5b6) will decrease coverage by 70.55%.
Report is 1 commits behind head on main.
The diff coverage is n/a.

@@              Coverage Diff              @@
##               main     #256       +/-   ##
=============================================
- Coverage     90.90%   20.36%   -70.55%     
- Complexity        0       97       +97     
=============================================
  Files             1      108      +107     
  Lines            11     2779     +2768     
  Branches          2      361      +359     
=============================================
+ Hits             10      566      +556     
- Misses            1     2169     +2168     
- Partials          0       44       +44     

see 107 files with indirect coverage changes

@github-actions
Copy link

Build available to test
Version: rehan-cleanup-tests-renaming-SNAPSHOT
Repository: https://s01.oss.sonatype.org/content/repositories/snapshots/

@mrehan27
Copy link
Contributor Author

Closing this PR due to change in our current priorities. We will revisit and reevaluate it once our ongoing projects are finalized.

@mrehan27 mrehan27 closed this Nov 13, 2023
@mrehan27 mrehan27 deleted the rehan/cleanup-tests-renaming branch November 13, 2023 09:11
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.

1 participant