-
Notifications
You must be signed in to change notification settings - Fork 222
Testing
We spend a lot of time making sure the code produces reliable software, but don’t take our word for it, explore our tests and execute them to see if the current codebase passes! The unit tests are constructed with help of the Check framework. If you’re interested in the entire QA and testing process you can read about it in the picoTCP testing article on our website. Let’s dive in!
Ensure that you have read the instructions on How to set up the environment
To compile and run the unit tests:
$ make clean; make units ARCH=faulty
$ ./test/units.sh
Looking for a guide on how to write new unit tests? See the wiki section Writing-unit-tests.
There are smoke tests as well, these make use of the virtual runnable picoapp with a VDE plug as ethernet driver. There’s a test script that runs multiple instances of picoTCP powered picoapps that will communicate with each other through the VDE plugs. Build with:
$ make clean; make test
This will create executable applications based on the examples provided. The applications are called build/test/picoapp.elf and build/test/picoapp6.elf
Now, if you want to run the autotest, type
$ sudo ./test/autotest.sh
Alternatively, if you want to run the application manually, check the Example application page.
Questions or remarks? Please contact us!
[email protected] | picotcp.altran.be | Twitter | Facebook
Getting Started
- Setting up the environment
- Testing
- Configuring and compiling
- Running picoTCP on Linux - Deprecated (see setting up)
- Running picoTCP on Windows
Porting
- Build process explained
- Porting the build to another compiler or IDE
- Porting picoTCP to your favorite embedded target
- Porting picoTCP to your favorite Operating System
- Example device driver
Development