Lines Matching full:tests

104 Automated Integration Tests
107 …test <https://docs.pytest.org/>`_ integration suite with some integration tests for ``esptool.py``…
109 …`esptool.py`` installed (see `Development Setup`_) in your environment in order to run these tests.
111 The following tests run automatically by GitHub Actions for each Pull Request. You can run them loc…
113 *  ``test_imagegen.py`` tests the ``elf2image`` command
114 *  ``test_image_info.py`` tests the ``image_info`` command
115 *  ``test_mergebin.py`` tests the ``merge_bin`` command
116 *  ``test_modules.py`` tests the modules used by ``esptool.py`` for regressions
117 *  ``test_espsecure.py`` tests ``espsecure.py`` functionality
119 The following tests are not run automatically by GitHub Actions, because they need real connected h…
121 *  ``test_esptool.py`` contains integration tests for ``esptool.py`` and needs to be run against re…
125    For example, to run all tests on an ESP32 board connected to /dev/ttyUSB0, at 230400bps:
129 …Or to run the TestFlashing suite only (using the pytest ``-k`` option to select tests based on the…
135       Some tests might fail at higher baud rates on some hardware.
137 The following tests are not run automatically by GitHub Actions, but can be run locally in a comman…
139 *  ``test_espefuse.py`` tests ``espefuse.py`` functionality. To run it:
147 …  Do not attempt to run these tests on real hardware! You risk damaging or destroying the ESP chip!
149 The whole test suite (without the tests needing an actual hardware) can be easily run with the foll…