News for hackers. Stuff that matters.
Re:Go 1.10 Release Notes by HankB99 on Saturday February 17, 2018 @09:45AM (#16400865)
In other words, there are ways to 'fool' the dependency tree. My first thought was that this might be a contrived situation. Then I realized I have exactly that in a project I'm presently working on. It does a lot of file system operations and I use shell scripts invoked from test code to set up files for testing. I'll have to investigate how to force tests to run if I change test scripts. I suppose changing the `go` test case to result in a test failure and then modifying the script to produce correct results (or a valid failure ;) ) would do the trick.

I guess changing the scripts would be detected by `go` so perhaps I don't have a problem. At present none of my scripts invoke other scripts.

Re:Go 1.10 Release Notes by HALtheWise on Sunday February 18, 2018 @10:36AM (#16406496)
Just read the scripts from your test function, then go will check their hashes and rerun the test if they changed.