Search
7 results for “FTWynn”
-
#PropertyTesting Pattern: Some things never change
Examples:
- Adding the same permissions to a user
- Removing a user from a group
- Changing a user preference -
#PropertyTesting Pattern: There and back again
Write properties that pair an operation with its opposite, so that you get the results you started with.
- Serializing and deserializing
- Toggling preferences / settings
- Writing and deleting an object from storage
- Adding and removing a fixed value from a Number -
#PropertyTesting Pattern: Different paths, same destination
If order truly doesn't matter, you should confirm that. Notable examples:
- Adding items in a cart (esp w/ & w/o sales)
- Changing user permissions
- Adding data sourcesTo test, generate a random set of operations to add and then check that the end state is what you expect.
-
If you're looking at putting #propertytesting into practice and drawing a blank once you open VSCode, this is the best article for direct advice.
I'll dive deeper into it over the week, because the examples can absolutely be expanded to services instead of just functions.
-
I'm more bearish on AI than most these days, but not a total hater. Justin and I walk through the nuance in the episode below.
-
There will be multiple sessions on Fault Injection at re:Invent this week as well! Worth a look if you'll be in Vegas this week.
-
I don't think I've posted about it anywhere else yet, so I'll mention it now.
I'm diving back into #OrgMode as my PKM of choice. It felt like most of the other apps today, evn if they support plaint text as a backend, have so much web tech sandwiched in between it was hard to actually change anything... and change is #emacs middle name.
It's funny because before I took Tiago's #BASB class the first time, I was on #OrgMode, but I ventured through several others before coming back.