Going crazy with Google tests
-
Just found an interesting question in SO. Some guy wants to apply Google tests to embedded STM32 program. To do this, they decided to write the STM32 HAL emulation (probably, to run such tests on a PC). Of course, after writing the whole HAL emulation (!!!) they have hundreds linker errors and want to know, how to fix them. But this is not a point. The interesting thing is the idea to make HAL emulation for running Google tests. Isn't this crazy? Finally, their hardware device will be part of some bigger thing. Like aircraft. After aircraft crash, they can say "But Google tests are OK!". In my company, when somebody tries to talk about Google tests for embedded programs, or code analysis for embedded programs (kind of Coverity, no goto please!), or Agile hardware development, I brutally refuse to talk about this. Hope this will never happen.
-
Just found an interesting question in SO. Some guy wants to apply Google tests to embedded STM32 program. To do this, they decided to write the STM32 HAL emulation (probably, to run such tests on a PC). Of course, after writing the whole HAL emulation (!!!) they have hundreds linker errors and want to know, how to fix them. But this is not a point. The interesting thing is the idea to make HAL emulation for running Google tests. Isn't this crazy? Finally, their hardware device will be part of some bigger thing. Like aircraft. After aircraft crash, they can say "But Google tests are OK!". In my company, when somebody tries to talk about Google tests for embedded programs, or code analysis for embedded programs (kind of Coverity, no goto please!), or Agile hardware development, I brutally refuse to talk about this. Hope this will never happen.
On a serious note, what are they going to use to Google test the HAL Emulator? :~
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony AntiTwitter: @DalekDave is now a follower!
-
Just found an interesting question in SO. Some guy wants to apply Google tests to embedded STM32 program. To do this, they decided to write the STM32 HAL emulation (probably, to run such tests on a PC). Of course, after writing the whole HAL emulation (!!!) they have hundreds linker errors and want to know, how to fix them. But this is not a point. The interesting thing is the idea to make HAL emulation for running Google tests. Isn't this crazy? Finally, their hardware device will be part of some bigger thing. Like aircraft. After aircraft crash, they can say "But Google tests are OK!". In my company, when somebody tries to talk about Google tests for embedded programs, or code analysis for embedded programs (kind of Coverity, no goto please!), or Agile hardware development, I brutally refuse to talk about this. Hope this will never happen.
11917640 Member wrote:
hundreds linker errors and want to know, how to fix them.
Carefully. Very, very carefully.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony AntiTwitter: @DalekDave is now a follower!
-
On a serious note, what are they going to use to Google test the HAL Emulator? :~
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony AntiTwitter: @DalekDave is now a follower!
-
They could write a meta-emulator which emulates the test environment for emulated HAL.
"Five fruits and vegetables a day? What a joke! Personally, after the third watermelon, I'm full."
"It's emulators all the way down!"
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony AntiTwitter: @DalekDave is now a follower!
-
Just found an interesting question in SO. Some guy wants to apply Google tests to embedded STM32 program. To do this, they decided to write the STM32 HAL emulation (probably, to run such tests on a PC). Of course, after writing the whole HAL emulation (!!!) they have hundreds linker errors and want to know, how to fix them. But this is not a point. The interesting thing is the idea to make HAL emulation for running Google tests. Isn't this crazy? Finally, their hardware device will be part of some bigger thing. Like aircraft. After aircraft crash, they can say "But Google tests are OK!". In my company, when somebody tries to talk about Google tests for embedded programs, or code analysis for embedded programs (kind of Coverity, no goto please!), or Agile hardware development, I brutally refuse to talk about this. Hope this will never happen.
11917640 Member wrote:
After aircraft crash, they can say "But Google tests are OK!".
They can say that, but that won't change anything; Google does not guarantee anything, and no judge will honor the dismissal of responsibility. If the crash was preventable, there's a possibility for criminal charges.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
Just found an interesting question in SO. Some guy wants to apply Google tests to embedded STM32 program. To do this, they decided to write the STM32 HAL emulation (probably, to run such tests on a PC). Of course, after writing the whole HAL emulation (!!!) they have hundreds linker errors and want to know, how to fix them. But this is not a point. The interesting thing is the idea to make HAL emulation for running Google tests. Isn't this crazy? Finally, their hardware device will be part of some bigger thing. Like aircraft. After aircraft crash, they can say "But Google tests are OK!". In my company, when somebody tries to talk about Google tests for embedded programs, or code analysis for embedded programs (kind of Coverity, no goto please!), or Agile hardware development, I brutally refuse to talk about this. Hope this will never happen.
Some guy on SO: *Writes a HAL emulation* Some guy on SO: *Builds the HAL emulation* HAL emulation: "I'm sorry Dave, I'm afraid I can't do that." Emulation success :D
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
