Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Hands-On Embedded Programming with C++17

You're reading from   Hands-On Embedded Programming with C++17 Create versatile and robust embedded solutions for MCUs and RTOSes with modern C++

Arrow left icon
Product type Paperback
Published in Jan 2019
Publisher Packt
ISBN-13 9781788629300
Length 458 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Maya Posch Maya Posch
Author Profile Icon Maya Posch
Maya Posch
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. Section 1: The Fundamentals - Embedded programming and the role of C++ FREE CHAPTER
2. What Are Embedded Systems? 3. C++ as an Embedded Language 4. Developing for Embedded Linux and Similar Systems 5. Resource-Restricted Embedded Systems 6. Example - Soil Humidity Monitor with Wi-Fi 7. Section 2: Testing, Monitoring
8. Testing OS-Based Applications 9. Testing Resource-Restricted Platforms 10. Example - Linux-Based Infotainment System 11. Example - Building Monitoring and Control 12. Section 3: Integration with other tools and frameworks
13. Developing Embedded Systems with Qt 14. Developing for Hybrid SoC/FPGA Systems 15. Best Practices 16. Other Books You May Enjoy

Testing code means trying to destroy it

A common mistake when writing tests is to write test scenarios that you expect will work. That's missing the point. While it's wonderful that a particular parsing routine did what it should do when it's handed perfectly formatted data, that's not very helpful in a real-life scenario.

While you can get perfect data, it's equally likely that you'll get completely corrupted or even garbage data in your code. The goal is to ensure that no matter what horrible things you do to the input data, it will never have a negative effect on the rest of the system.

All input should be validated and sanity checked. If something doesn't seem right, it should be rejected rather than you allowing it to cause issues elsewhere in the code later on.

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image