TDD for Embedded C
2018-10-26 15:29:19 UTC
Most useful learnings:
Bits and pieces about testing. I read James's book a few years ago so I heard most of the concepts already, but it was a very useful reminder.
Concepts v exercises:
Not enough exercises
Presentation v discussion:
I didn't like the legacy part (3rd day), because it felt unstructured and not that clear. I didn't know anything about the presented legacy projects so it was boring.
I loved the exercises and I would only like to see more of them. The exercises were very structured (great for beginners), but some of them could be less structured so that we learn about how to start testing (creating our own test files etc.)
One of the useful exercises could be downloading cppunit testing framework to our computers, writing some simple code and then try to test it.
James is engaging and approachable.
Not really - there are so many types of tests and ways of testing that I feel a bit overwhelmed. Another issue is trying to download the cppunit test framework and making it to work in Visual Studio (unsuccessful so far, so I imagine it will take time).
Challenges to applying:
Our team is using existing "test frameworks" (a poor and limited framework built in Matlab) that is used for module testing. There are also some oversea contractors from India that are used to their ways of testing the code (also poor) and they also have their way of writing code. All of this makes it difficult to switch to a more powerful framework because it is expected of us to have a standardised way of testing and writing code followed by everyone. More powerful framework would mean a learning curve for everyone and some people might not want to do it (or it would involve training).
It felt a bit unstructured - I would like to see an overview of all the test types in cppunit (or in general), differences between them and scenarios where some might be better than others.
Legacy code workshop:
Recommend to others: