FastExperimenter
|
GWT Test Gen
Star this Commitment
FastExperimenter commits to:
Given this week and 10 hour workdays.
When each workhour comes Then I* design 10 "Given, When, Then (Result)" tests in my mind each workhour.
No more reports due
|
My Commitment Journal
 FastExperimenter
June 29, 2018, 12:31 PM
|
|
|
I*'m happy with this process. It's super helpful when you have a vague action list. You can GWT it, and all the sudden you have pass/fail criteria for your action, and you can tell if you're making progress or not. For example: > Math... turns into... G: Math W: I* choose to do math (06:30) T: Open the text, take al remaining problems (marked out from the last session in blue), divide time (1h30m) among remaining problems. (Dis)Solve them in a way congruent with my values. For some reason, this was really helpful. I procrastinated for a recorded 1h28m on YouTube. When I wrote down the GWT (in addition to some value clarification), the engine fired up, and I* got enough velocity to leave the tarmac. Was smooth sailing from there. Notable thoughts: When it gets tough, looking at the time never helps. Only doubling down into your process, giving it more energy, focus, attention, will relieve the pain (and maybe make you enjoy it). |
|
|
FastExperimenter
June 28, 2018, 10:35 AM
|
|
| (I*'ve also used dragon-petting thinking, for the below comment.) | |
|
FastExperimenter
June 28, 2018, 10:35 AM
|
|
|
This is a low-medium difficulty, valuable exercise. I* got 6 in for the first hour, but I* overtook this deficit where I had a few hours with more GWT's than usual. Also, there's something else that should be taken into account. There's some purpose this serves. There's something you expect to happen. It's to verify that what you expect actually happens. Then, when you do it, and if it doesn't, then you can behave better in the future. The major benefit of this is it determines what actions I* should take. It eliminates so many actions by being crystal clear on a few dimensions of the outcome, and then it adds something else. It's like, "What pokes what, and what happens?" Maybe the goal is to ID the things that I* should poke. What are all the things that other things can poke, and what are the expectations I* have for when I* poke them? But, it still feels like there's something else I* need to consider. I*'ve tried focusing on an aim. But, every time I* try to focus on the aim, but it still seems rough. Maybe I* need to be more firm on the outcome I*'m after, long-term. I*'m trying to use this to guide my thinking and improve. I*'m trying to use this to become a better person, sharpen my thinking. I*'ve used chaos-to-order thinking, CSQ, values consideration, in conjunction with this. Hold on, the Google may have helped me big time. It talks about finding bugs, defects. It talks about how testing is to "verify and validate that the product meets the stated requirements/specifications" I* need to have requirements or specifications before I* test. This is obvious and awesome because I* can make my tests more useful, by determining what my requirements/specs are before testing, instead of just jumping into testing! |
|
|
FastExperimenter
June 26, 2018, 12:30 PM
|
|
|
I'm learning ideas at work faster using this. And for coding: Example test. "GIVEN tests to do and PHPUnit WHEN I* need a test done. THEN I* write it competently in a PHP Unit." Also, maybe I* could try passing this test by building a bunch of smaller(?) related tests. Then, once I*'ve passed these smaller, supportive tests, see if I* can't actually hit the original test more easily. "GIVEN PHPUnit and namespace (or class, extends, implements...) WHEN I* think about a namespace. Then I* understand it and know what to do to use it (in my tests)" Future action: Set up big test. If big test not done quickly, set up supportive tests. Do what's needed to pass these supportive tests (read, listen, learn, experiment). Then revisit the big test and see if I* don't pass that test (or can't easily pass that test). Repeat starting at "Set up supportive tests." (I may have revised this a few times.) |
|
This Commitment has no photos.
Displaying 1-1 of 1 result.
June 26 to June 29
Successful
Success
.
