-
Notifications
You must be signed in to change notification settings - Fork 304
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
Feature/unit testing #1013
Feature/unit testing #1013
Conversation
Download the artifacts for this pull request: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@brianignacio5 hi ! Tested: Click "Testing" in the Activity Bar -> The tests automatically found in the current workspace folder. 👍
|
@brianignacio5 hi ! Tested under: Issue still persist.
|
Pull request has been marked as |
a769152
to
10d769e
Compare
@brianignacio5 hi ! Issue still persist. I can run the test but test runs forever and there is no results and any output in terminal. |
fc5a639
to
873bbfb
Compare
@brianignacio5 hi ! Tested under: Able to run tests with ESP32 board connected. output also clear.
LGTM 👍 |
Description
Add Unit testing from ESP-IDF extension using PyTest from ESP-IDF.
TO-DO: Add fallback PyTest requirements.
Fixes #485
Type of change
Steps to test this pull request
Open an example project that has esp-idf tests as described in Unit Testing in ESP32. For example use the unit test example
Expected behaviour: Tests output is shown as Task Output and the result is shown in the Testing UI (passed/ failed)
Expected output: Test execution output is shown as task output.
How has this been tested?
Test Configuration:
Dependent components impacted by this PR:
Checklist