8000 Unskip some tests, delete others by antocuni · Pull Request #1742 · pyscript/pyscript · GitHub
[go: up one dir, main page]

Skip to content

Unskip some tests, delete others #1742

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

Merged
merged 15 commits into from
Sep 25, 2023
Merged

Unskip some tests, delete others #1742

merged 15 commits into from
Sep 25, 2023

Conversation

antocuni
Copy link
Contributor
@antocuni antocuni commented Sep 21, 2023

This is another PR which aims to clean up a bit the testsuite and integration tests.
Highlights:

  • Some of the @skipped tests just worked -- I unskipped them
  • some worked after some small tweak to adapt to the new pyscript next
  • some are still skipped, but I tweaked the skip message to be more precise and descriptive

Moreover, I killed/removed the ones which no longer make sense in the context of pyscript next; in particular, I removed all the ones which tested Element (which is now gone) and the one which tested py-config features which are no longer needed (e.g., multiple interpreters).

The testsuite passes locally.

I plan to open an umbrella issue where to keep track of the remaining skipped/xfailed tests, so be handled after the release of RC1

@WebReflection
Copy link
Contributor

I love this PR and I badly want this in but we had this discussion with Fabio before and there was no super clear outcome ... the pyweb might offer similar Element functionalities and it'd be a pity to lose all these tests and code until we're sure al of those are really useless ... I'd rather wait for him to move this forward but you have my virtual 👍 on this!

@antocuni
Copy link
Contributor Author

I love this PR and I badly want this in but we had this discussion with Fabio before and there was no super clear outcome ... the pyweb might offer similar Element functionalities and it'd be a pity to lose all these tests and code until we're sure al of those are really useless ... I'd rather wait for him to move this forward but you have my virtual 👍 on this!

I assumed that pyweb had its own tests, but I admit I didn't check.

@@ -81,12 +81,12 @@ def test_script_type_py_src_attribute(self):
)
assert self.console.log.lines[-1] == "hello from foo"

@pytest.mark.skip("FIXME: test failure is unrelated")
@pytest.mark.skip("FIXME: wait_for_pyscript is broken")
Copy link
Contributor

Choose a reason for hiding this comment

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

I assume wait_for_pyscript is broken for the same execution-order reasons? Or is it more generally broken? Again, really just curious for later.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I assume wait_for_pyscript is broken for the same execution-order reasons? Or is it more generally broken?

yes, it's the same problem.
The problem is that the current version of wait_for_pyscript() waits for PyScript Ready which is printed before the tags are executed, not after.

Basically right now all the tests are at risk of being flaky, but most of them are just fast enough that they work in practice.

Copy link
Contributor
@JeffersGlass JeffersGlass left a comment

Choose a reason for hiding this comment

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

LGTM! Thanks for updating the skip notes on these - sounds like some fruitful things to investigate.

@antocuni antocuni merged commit b9a1227 into main Sep 25, 2023
@antocuni antocuni deleted the antocuni/unskip-more-tests branch September 25, 2023 16:14
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.

3 participants
0