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

fix(tests): Fix wrong selection of tests and add debug flag for testing #10583

Merged
merged 2 commits into from
Nov 8, 2024

Conversation

lucasssvaz
Copy link
Collaborator

@lucasssvaz lucasssvaz commented Nov 7, 2024

Description of Change

Using the -k flag in the pytest command might run more than the selected test. For example using -k test_psram will run both test_psram and test_psramspeed. To fix this we can directly pass the python file for the test.

Also, to help with testing, added a -d flag to the compilation process. This will be useful to compile tests with debug logs enabled. For example:

./.github/scripts/tests_build.sh -s uart -t esp32 -d verbose

Tests scenarios

Tested locally

Copy link
Contributor

github-actions bot commented Nov 7, 2024

Messages
📖 🎉 Good Job! All checks are passing!

👋 Hello lucasssvaz, we appreciate your contribution to this project!


Click to see more instructions ...


This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...


We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 02bec1a

Copy link
Contributor

github-actions bot commented Nov 7, 2024

Test Results

 56 files   56 suites   4m 22s ⏱️
 21 tests  21 ✅ 0 💤 0 ❌
134 runs  134 ✅ 0 💤 0 ❌

Results for commit c7c4f68.

♻️ This comment has been updated with latest results.

@lucasssvaz lucasssvaz marked this pull request as ready for review November 7, 2024 23:17
@me-no-dev me-no-dev added the Status: Pending Merge Pull Request is ready to be merged label Nov 8, 2024
@me-no-dev me-no-dev merged commit 09a6770 into espressif:master Nov 8, 2024
36 of 44 checks passed
@lucasssvaz lucasssvaz deleted the test/wokwi_fixes branch November 8, 2024 11:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Pending Merge Pull Request is ready to be merged Type: CI & Testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants