IEnumVARIANT Test Case #101
Conversation
* Add helper for getting single displayID for dispatch.
|
I always surprised at your test or release management that was exactly. |
|
@mattn I am not sure what you mean. My attempt was to get it to where you can determine whether a pull request was stable or damn near stable enough with whether the CI breaks. It is useful. I do tend to push before the code is ready just so that I can start testing. I find it is better and faster to just test locally. I'm almost done with Destiny and should be done with Assassin's Creed. I think I have a better handle with the last few test cases that I will start doing that again. I just hope that more people write test cases in their pull requests, because you can never have too many good test cases. Release management is really just trying to keep master as stable as possible. Given that, as you know, The test is supposed to really use the C# COM server, because then you know that the functionality will always be available. Whereas, querying other Program IDs or GUIDs might not exist and therefore the tests will fail. I think I'm going to have to implement The problem was that I wasn't able to figure out if the tests were failing because WMI class ID doesn't exist or if the test case is incorrect. |
Because you have doing things that I am not good, I always grateful to you. And always surprised to your accuracy works. 👍 |
|
@mattn Thanks man. I'm just experimenting with how to properly program. It is nice that you think what I'm doing is good. That means I'm getting better. |
|
I'm going to break changes out and do separate merge requests. Also needs to squash commits. |
…ariant_testcase Conflicts: ienumvariant_windows.go
…ariant_testcase Conflicts: ChangeLog.md
Adds basic IEnumVariant test case.