Thanks for this talk. Really informative. Have a question: When we say legacy code they are really legacy code and are not well written in the sense that non UI code is being mixed heavily with UI code. For example ui widget being updated from a slot by a device specific signal which won’t work without building the device code and having the device connected. It isn’t easy to separate unless we do some mods to mock the device signals which seems like we’ll be changing quite a lot of code to get one single test going. What would you suggest in such a scenario ? Thanks
This is only true if you link the Qt Libraries statically, this was never mentioned in the video i think. The static linking in the video is about your own code, you should separate the code from the executable to easily link it into the executable and the test(s)
Thank you very much for the talk!
Thanks for this talk. Really informative. Have a question: When we say legacy code they are really legacy code and are not well written in the sense that non UI code is being mixed heavily with UI code. For example ui widget being updated from a slot by a device specific signal which won’t work without building the device code and having the device connected. It isn’t easy to separate unless we do some mods to mock the device signals which seems like we’ll be changing quite a lot of code to get one single test going. What would you suggest in such a scenario ? Thanks
Unfortunately for static linking you need to buy a commercial license of Qt...
This is only true if you link the Qt Libraries statically, this was never mentioned in the video i think.
The static linking in the video is about your own code, you should separate the code from the executable to easily link it into the executable and the test(s)