Add tests for pyproject with multiple readme files

[wagnerluis1982]

Pull Request Check List

tests/masonry/builders/test_editable_builder.py

• Checks if content of all readme files are printed to the metadata

tests/console/commands/test_build.py (new file)

• Checks sdist file exists and is not empty
• Checks wheel file exists and is not empty
• Checks inside sdist tar file if contains all readme files

Closes: #6633
Depends on: python-poetry/poetry-core#551

• This PR only add tests

[wagnerluis1982]

Question to maintainers, does poetry have any integration test for poetry build command? I was not able to found any.

[radoering]

Probably not. (It should be located at tests/console/commands.)

Since the test in this PR is passing even without the poetry-core fix, I assume an integration test is required to provoke the issue?

[wagnerluis1982]

@radoering Exactly, that's why I was looking for an integration test for build.

I will create a new test module then.

[wagnerluis1982]

Just added a test to verify poetry build command.

NOTE: the pipeline is going to fail until python-poetry/poetry-core#486 is merged.

[wagnerluis1982]

Hi @radoering, after you merged python-poetry/poetry-core#486, I expected the tests to not fail (I just rebased after master).

I expected the pipeline to use latest poetry-core version. Does that happen?

[radoering]

No, it just uses the locked version of poetry-core (no magic). Normally, we just update the locked version after a core release.

[wagnerluis1982]

No, it just uses the locked version of poetry-core (no magic). Normally, we just update the locked version after a core release.

No magic 🙁

In that case, it would be advisable to reopen issue #6633 to signalize users, IMHO.

[wagnerluis1982]

@Secrus the tests here are going to fail while next poetry-core isn't released.

[wagnerluis1982]

@radoering when you have a chance, please check this.

Now that poetry-core 1.5.0 is locked, the tests are passing.

[radoering]

Just some minor nitpicks.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.