esp-idf/examples/protocols/asio/ssl_client_server/example_test.py

from __future__ import unicode_literals

import ttfw_idf


@ttfw_idf.idf_example_test(env_tag='Example_GENERIC', target=['esp32', 'esp32c3'])
def test_examples_asio_ssl(env, extra_data):

    dut = env.get_dut('asio_ssl_client_server', 'examples/protocols/asio/ssl_client_server')
    dut.start_app()

    dut.expect('Reply: GET / HTTP/1.1')


if __name__ == '__main__':
    test_examples_asio_ssl()
examples: asio ssl example demonstrating both server and client By default it uses simple client connecting to https address. It is possible to configure both server and client. As for example test the configuration of both server and client connecting to each other on 2020-06-05 16:19:10 +02:00			`from __future__ import unicode_literals`
style: format python files with isort and double-quote-string-fixer 2021-01-26 10:49:01 +08:00
examples: asio ssl example demonstrating both server and client By default it uses simple client connecting to https address. It is possible to configure both server and client. As for example test the configuration of both server and client connecting to each other on 2020-06-05 16:19:10 +02:00			`import ttfw_idf`


ci: run Example_GENERIC for C3 Add support for running example_GENERIC tests for C3 on label. Fix examples that fail. 2021-03-12 14:05:17 +08:00			`@ttfw_idf.idf_example_test(env_tag='Example_GENERIC', target=['esp32', 'esp32c3'])`
examples: asio ssl example demonstrating both server and client By default it uses simple client connecting to https address. It is possible to configure both server and client. As for example test the configuration of both server and client connecting to each other on 2020-06-05 16:19:10 +02:00			`def test_examples_asio_ssl(env, extra_data):`

			`dut = env.get_dut('asio_ssl_client_server', 'examples/protocols/asio/ssl_client_server')`
			`dut.start_app()`

			`dut.expect('Reply: GET / HTTP/1.1')`


			`if __name__ == '__main__':`
			`test_examples_asio_ssl()`