I am not 100% ready to abandonTest, Guess, and Go. Amazingly I still have readers and Google links my posts to searches for things like Tandem occlusion alarms. I periodically get emails from people wondering if I am okay since I haven’t written in so long. Once in a while I have ...
Pingback: Conversations: Two Type 1 Diabetics Have a Chat | Test Guess and Go Leave a comment Write a comment... Log in or provide your name and email to leave a comment. Email me new posts Instantly Daily Weekly Email me new comments Save my name, email, and website in this browse...
Unlock Your Potential Grow into the person you want to be with your optional Premium Suite. Question 1 of 60: You regularly make new friends. You regularly make new friends. Agree Disagree Question 2 of 60: Complex and novel ideas excite you more than simple and straightforward ones. ...
So: "I passed", and this, if you can guess, is in the past tense because of the "ed". "I passed my test with flying colours." And so, in the American or Canadian system, this would mean you got an "A" or an "A+". You did very, very well. Similarly, sometimes we talk ...
First, there is no good way to guess how long to wait before attempting to access the Form object. So you must be conservative and put in a very long delay time, which slows your test automation significantly, especially if you are running hundreds or thousands of test cases. Second, ...
We still have to go through a fix cycle to get all the bugs worked out and more regression testing to verify fixes and already tested functionality.A question I often ask to development is how long do they think it will take to fix the bugs that the testers find.We also ship based on...
func (c *Config) GetProwJobDefault(repo, cluster string) *prowapi.ProwJobDefault { return c.mergeProwJobDefault(repo, cluster, nil) } // GuessDefaultDecorationConfig attempts to find the resolved default decoration // config for a given repo and cluster. It is primarily used for best ...
First, there is no good way to guess how long to wait before attempting to access the Form object. So you must be conservative and put in a very long delay time, which slows your test automation significantly, especially if you are running hundreds or thousands of test cases. ...
First, there is no good way to guess how long to wait before attempting to access the Form object. So you must be conservative and put in a very long delay time, which slows your test automation significantly, especially if you are running hundreds or thousands of test cases. Second, ...
My reading of this issue is that go test -cover should always output a percentage if it succeeded. That's the current issue title, but that behavior seems clearly wrong if there are no statements to cover: 0/0 is not a well-defined percentage. (I guess we could output NaN%, but that...