Interaction Tests, Mocks & Refactoring in Embedded Software (Udemy.com)

The tools are rather outdated. The container image contains Ubuntu 18.04, which cannot be connected to VSCode. I had to upgrade it to Ubuntu 20.04. I think either redoing the chapter or adding some extra material explaining how to connect the container to VSCode, so that you don't have to map the folder to your computer (in my case, the container is running under wsl) would be convenient, plus upgrading the container's image. Also I think the training tries to focus on too many topics (TDD, design patterns, refactoring...) when maybe some people are just more interested in a particular subject (in my case, CMock) and not so interested in building the actual functionality (for example, the whole HAL and low level).

Best course on TDD. I really loved the separation in iterations and increasing complexity. The course material is still relevant and no hardware is needed. Do not expect to get your hand holded, this course handles advanced material for anybody with some TDD experience.

Bad teaching and illustration methods. Non-organized content. Messy course!

Great course, material is definitely still relevant. The instructors are great, and are extremely responsive and helpful, which I really appreciate. The only downside is that the NXP LPC1768 board, although not required, is discontinued. It would have been great to test it on an actual board.

Well this is one of the best courses I've ever taken. It is like looking over the shoulder of an experienced engineer, and this is way more then I expected from this course. It also teaches you some SW development design practices. Ever heard of the saying: "Weeks of coding can save you hours of planning"? These guys also give you the knowledge of the hours of planning, which is very uncommon and very much appreciated. This course is demanding - so if you think that it is only a couple of hours of videos - this is not it. If you really want to learn this stuff it will take you much longer, but the instructors really try to grain it into you. You just need to do the work ;) Anyway - thank you for this brilliant course.

Some very useful design patterns and practices for bare-metal applications were presented. Using a real-world project instead of individual toy examples is definitively a plus. However, the mbed NXP LPC1768 board used seems to have been discontinued. A video explaining the why, when and how of using simulators is sorely needed, as it was not until after finishing the course that I realized I had been using a cross-compiler and simulator the whole time. I had to dig through the throwtheswitch forum to get an idea of what the simulator was even doing. ----------- EDIT: After having completed a significantly more expensive course on another platform, and with my new-found appreciation for the architectural patterns taught in this course, I felt obligated to come back and bump up the rating to a full five stars. Please make a course about DevOps for embedded systems!

As an embedded developer who spent years writing his own HAL drivers for micro-controllers but working in a small company where formal unit testing didn't exist, and now working for a big company in a bigger team where TDD and unit testing is heavily used, this course is an excellent tool to help me transition from things I am already familiar with to formal unit testing practices. Also these guys are very clear and easy to understand and excellent teachers, and the little bit of humor along the way makes it even more fun. Highly recommend this course!

This course goes in depth with more than just interaction testing and mocking. I appreciated learning not just the concepts but also how to use a practical build tool: Ceedling. The development environment is fantastic, using a Docker container is cross platform and easy to use. The design patterns taught and how to apply them was very helpful. Delivery is also fantastic. Mark and Mike are engaging, funny, and on point! There is plenty of work here to test your testing skills on. There might be 7 hours of lectures, but time in total would easily be >24 hours (writing code and tests, and a bit of on target debugging, which the course does not cover). I am looking forward to a third course, which hopefully will cover system and on target testing!

There were very nice examples and pattern and best practices explained and handled. The huge amount of code around it made it at a certain point too heavy to take in. I'm a programmer for about 30 years, I know how to setup architectures and how to program. I would have liked a shorter version (with less coding) only explaining how to fit TDD, CMOCK and Ceedling in a project instead of working out a complete project.

I was happy with the first course but when I tried to apply Ceedling in my own personal projects, it didn't take long to realize that I didn't know enough and there was still much to learn. This second course covers a lot of the missing pieces, mocks being the prime example. This second course is also very good. It's much longer and requires more effort, skill, and commitment from the student.