-
Notifications
You must be signed in to change notification settings - Fork 87
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
OCPP E2E tests #959
OCPP E2E tests #959
Conversation
…ry ocpp_tests/ Signed-off-by: Piet Gömpel <pietgoempel@gmail.com>
Also install it in editable mode Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
…gnature validation This also fixes OCPP 1.6 ocpp_compliance_tests.py:test_signed_update_firmware Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
…ion-tests Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
…be the everest install directory Signed-off-by: Piet Gömpel <pietgoempel@gmail.com>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Signed-off-by: Piet Gömpel <pietgoempel@gmail.com>
Signed-off-by: Piet Gömpel <pietgoempel@gmail.com>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Signed-off-by: Piet Gömpel <pietgoempel@gmail.com>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Signed-off-by: Piet Gömpel <pietgoempel@gmail.com>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
|
Piet pointed me to the requirements.txt in tests/ocpp, where the first point is already 'done' (those packages are in there) |
I would like to have an sh script to run all tests and that it is not needed to go to different folders. Would that be an option? |
echo "Running $PARALLEL_TESTS tests in parallel" | ||
|
||
# run all tests in parallel | ||
"$PYTHON_INTERPRETER" -m pytest -d --tx "$PARALLEL_TESTS"*popen//python="$PYTHON_INTERPRETER" -rA --junitxml=result.xml --html=report.html --self-contained-html --max-worker-restart=0 --timeout=300 --dist loadgroup test_sets/ocpp16/*.py test_sets/ocpp201/*.py --everest-prefix "$EVEREST_CORE_DIR/build/dist" |
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.
It is nice to be able to run all tests in parallel. Is it possible to add this as an environment variable so you can choose how many processors are used? Instead of always using all of them for the tests.
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.
you can already run e.g.
./run-testing.sh 4
to run with 4 workers.
tests/ocpp_tests/README.md
Outdated
If you run the test cases individually, | ||
make sure to have all required certificates and configs | ||
for the test cases installed using the | ||
convenience scripts inside [test_sets/everest/aux](test_sets/everest-aux/) |
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.
It is not clear to me where this everest-aux directory is. It is not in test_sets.
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.
it is in tests/ocpp_tests/test_sets/everest-aux
. The path was wrong ;)
Looks good, only one thing in the documentation and some other remarks, but maybe those are good for the clean-up issue |
Signed-off-by: Piet Gömpel <pietgoempel@gmail.com>
@@ -54,7 +62,7 @@ specified in `test_sets/ocpp201/remote_control.py`. | |||
If you run the test cases individually, | |||
make sure to have all required certificates and configs | |||
for the test cases installed using the | |||
convenience scripts inside [test_sets/everest/aux](test_sets/everest-aux/) | |||
convenience scripts inside [test_sets/everest-aux](test_sets/everest-aux/) |
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.
Isn't the everest-aux directory in another repo (everest-framework or something)? I could not find it in the test_sets directory of everest-core.
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.
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.
it's even in the pull request :D. Oops.
Might have searched for everest_aux or something indeed.
dependencies.yaml
Outdated
@@ -86,7 +86,7 @@ ext-mbedtls: | |||
# everest-testing and ev-dev-tools | |||
everest-utils: | |||
git: https://github.com/EVerest/everest-utils.git | |||
git_tag: v0.4.2 | |||
git_tag: 9c7a4928251f47ffb7f8197f6cba8596fd15d242 |
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.
this needs to point to released version of everest-utils not a commit on a branch
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.
One more addition to the readme: can you add there that you have to start mosquitto? |
Is it possible to also add the california pricing and display message tests by the way? |
Sure you can add them here. In case they cause issues we can also add them in a subsequent PR. |
Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Describe your changes
This PR adds OCPP1.6 and OCPP2.0.1 E2E tests to everest-core.
TODOs:
Issue ticket number and link
This issue summarizes todos to clean up the ocpp tests with subsequent PRs
Checklist before requesting a review