OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/tests/net/lib/mqtt_packet/prj.conf

14 lines
252 B
Plaintext
Raw Normal View History

iot/mqtt: Add test app for the MQTT packet handling routines The following routines are evaluated in this test case: - mqtt_pack_connect - mqtt_pack_disconnect - mqtt_pack_publish - mqtt_pack_subscribe - mqtt_pack_suback - mqtt_pack_pingreq - mqtt_pack_pingresp - mqtt_pack_puback - mqtt_pack_pubcomp - mqtt_pack_pubrec - mqtt_pack_pubrel - mqtt_pack_unsuback - mqtt_unpack_connect - mqtt_unpack_disconnect - mqtt_unpack_pingreq - mqtt_unpack_pingresp - mqtt_unpack_puback - mqtt_unpack_pubcomp - mqtt_unpack_pubrec - mqtt_unpack_pubrel - mqtt_unpack_unsuback Future patches will extend this test case to cover the whole MQTT packet library. Origin: Original Jira: ZEP-870 Change-Id: I4fee403c24d1eb0428fb18b413763e28b6b726d1 Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2016-11-08 14:24:53 +08:00
# required for htons
CONFIG_NETWORKING=y
net: enable SLIP only on QEMU targets In many networking tests we had to configure SLIP in the prj.conf leaving those configurations Qemu specific. This change enables SLIP for QEMU targets automatically and allows reuse of prj.conf for multiple boards. Additionally, the TUN options is removed. This option was not used anywhere. To enable self-contained networking tests that do not depend on SLIP, we introduce the new option NET_TEST which disables TAP and allows testing in QEMU without the need for a host interface. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-07-26 20:45:13 +08:00
CONFIG_NET_TEST=y
iot/mqtt: Add test app for the MQTT packet handling routines The following routines are evaluated in this test case: - mqtt_pack_connect - mqtt_pack_disconnect - mqtt_pack_publish - mqtt_pack_subscribe - mqtt_pack_suback - mqtt_pack_pingreq - mqtt_pack_pingresp - mqtt_pack_puback - mqtt_pack_pubcomp - mqtt_pack_pubrec - mqtt_pack_pubrel - mqtt_pack_unsuback - mqtt_unpack_connect - mqtt_unpack_disconnect - mqtt_unpack_pingreq - mqtt_unpack_pingresp - mqtt_unpack_puback - mqtt_unpack_pubcomp - mqtt_unpack_pubrec - mqtt_unpack_pubrel - mqtt_unpack_unsuback Future patches will extend this test case to cover the whole MQTT packet library. Origin: Original Jira: ZEP-870 Change-Id: I4fee403c24d1eb0428fb18b413763e28b6b726d1 Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2016-11-08 14:24:53 +08:00
# native IP stack support
drivers: Rename `random` to `entropy` This should clear up some of the confusion with random number generators and drivers that obtain entropy from the hardware. Also, many hardware number generators have limited bandwidth, so it's natural for their output to be only used for seeding a random number generator. Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
2017-10-14 07:30:55 +08:00
CONFIG_ENTROPY_GENERATOR=y
iot/mqtt: Add test app for the MQTT packet handling routines The following routines are evaluated in this test case: - mqtt_pack_connect - mqtt_pack_disconnect - mqtt_pack_publish - mqtt_pack_subscribe - mqtt_pack_suback - mqtt_pack_pingreq - mqtt_pack_pingresp - mqtt_pack_puback - mqtt_pack_pubcomp - mqtt_pack_pubrec - mqtt_pack_pubrel - mqtt_pack_unsuback - mqtt_unpack_connect - mqtt_unpack_disconnect - mqtt_unpack_pingreq - mqtt_unpack_pingresp - mqtt_unpack_puback - mqtt_unpack_pubcomp - mqtt_unpack_pubrec - mqtt_unpack_pubrel - mqtt_unpack_unsuback Future patches will extend this test case to cover the whole MQTT packet library. Origin: Original Jira: ZEP-870 Change-Id: I4fee403c24d1eb0428fb18b413763e28b6b726d1 Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2016-11-08 14:24:53 +08:00
CONFIG_TEST_RANDOM_GENERATOR=y
# enable the MQTT lib
tests: mqtt: Port tests to use new implementation Port existing MQTT tests to new socket MQTT API. Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
2018-09-19 19:37:24 +08:00
CONFIG_MQTT_LIB=y
tests: mqtt_packet: convert to ztest - replaced test points with ztest APIs wherever possible JIRA: ZEP-2249 Signed-off-by: Niranjhana N <niranjhana.n@intel.com>
2017-08-08 18:28:59 +08:00
CONFIG_ZTEST=y
tests: CONFIG_TEST_USERSPACE now off by default Unlike CONFIG_HW_STACK_PROTECTION, which greatly helps expose stack overflows in test code, activating userspace without putting threads in user mode is of very limited value. Now CONFIG_TEST_USERSPACE is off by default. Any test which puts threads in user mode will need to set CONFIG_TEST_USERSPACE. This should greatly increase sanitycheck build times as there is non-trivial build time overhead to enabling this feature. This also allows some tests which failed the build on RAM-constrained platforms to compile properly. tests/drivers/build_all is a special case; it doesn't put threads in user mode, but we want to ensure all the syscall handlers compile properly. Fixes: #15103 (and probably others) Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2019-04-06 06:39:50 +08:00
CONFIG_TEST_USERSPACE=y
tests: net: Increase the stack size of frdm-k64f The icmpv6, http_header_fields, mqtt_packet, dns_packet and net utils tests were failing in frdm-k64f because of too small stack. Fixes #8171 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2018-06-05 18:42:39 +08:00
CONFIG_MAIN_STACK_SIZE=1280