• Workshop name: Legacy Code Workshop
  • Course code: MARV-1
  • Workshop days: 0.5
  • Your workshop: We watch first driver and instructor working on our function for the first three hour. Then took a break and changed driver. Before break, it could be built. But when we got the whole file directory, it could not build. It took us a while to continue working on, though we were all use Win10, but the linux various, first driver was using WSL, I was using cygwin, second driver was using SAMBA connected to ubuntu. When second driver solved all the complain of compiler and ran, it just failed as expectation. Then we found that failed point was a shared memory. So we had a homework to figure it out how to solve this. We didn't have enough time to write any test for our code.
  • Better prepared: Much better
  • How to improve: 1. Have same setup on CPPUTEST. There is a lot of option to setup cpputest environment, having same setup may have less trouble when changing driver. (shared the same server, or all use docker... etc) 2. Give some brief instruction to choose function Before workshop, we had asked day1 participant about their experience, they gave us some advices to have a easier function. We thought we already choose a simple function, but still took a lot of time to solve independency.
  • Recommended: Yes
  • Quote permission: Yes
  • Back