Skip to content

Testing with source code from other repositories #9290

Closed

Description

@sosukesuzuki

We run the latest Prettier on the other repositories' source code to check for regressions before we release.

like below:

This is hard to do manually, so I want to automate it.

Activity

  1. added
    type:testsIssues about tests that are not correct, should be added, or similar
    on Sep 29, 2020
  2. self-assigned this
    on Sep 29, 2020
  3. fisker commented on Sep 29, 2020

    @fisker
    Member

    Use a separate repo,

    • add prettier/prettier and other repositories as submodule.
    • add GithubActions, when open an issue with specific title(or other events), CI send a PR with formatted code.
  4. sosukesuzuki commented on Sep 29, 2020

    @sosukesuzuki
    MemberAuthor

    What do you think about adding to this repository as a integration test and checking with a CI for each PR?

  5. fisker commented on Sep 29, 2020

    @fisker
    Member

    Will this test fail, if format changed? Or are you thinking about snapshot the result?

  6. sosukesuzuki commented on Sep 29, 2020

    @sosukesuzuki
    MemberAuthor

    Sorry, I was mistaken. I'll try with your suggestion.

  7. sosukesuzuki commented on Oct 1, 2020

    @sosukesuzuki
    MemberAuthor

    I created a repository https://github.com/sosukesuzuki/prettier-regression-testing.
    I don't know the way to see diffs of submodules on PR. So, I implemented an action using issue comments for checking diffs. See example issue: sosukesuzuki/prettier-regression-testing#4.
    This has only typescript-eslint as a submodule because work in progress.

  8. fisker commented on Oct 1, 2020

    @fisker
    Member

    Maybe no submodule, git clone -> git commit -> run format -> git commit?

  9. sosukesuzuki commented on Oct 1, 2020

    @sosukesuzuki
    MemberAuthor

    Hmm, we want to see just diffs. So I think submodule and issue comments is enough. They are also relatively easy to manage.

  10. fisker commented on Oct 1, 2020

    @fisker
    Member

    I don't know how to see submodule diff either.

    git clone -> git commit -> run format -> git commit

    We can check the second commit to see diff.

  11. sosukesuzuki commented on Oct 1, 2020

    @sosukesuzuki
    MemberAuthor

    I don't know how to see submodule diff either.

    sosukesuzuki/prettier-regression-testing#4 (comment)

    I'll use it to check regressions in the next release. If we are unhappy with it, you can improve it afterwards.
    I close this issue for now.

  12. locked as resolved and limited conversation to collaborators on Dec 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

locked-due-to-inactivityPlease open a new issue and fill out the template instead of commenting.type:testsIssues about tests that are not correct, should be added, or similar

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions