@usgraphics@htmx_org >> core that regressions will be clearly evident when using the product or in integration/e2e tests. When that happens, you can add tests to make sure it doesn't happen again
@usgraphics@htmx_org The code base I work on owes its stability and quality to its comprehensive test suite, but in many cases I agree. I don't think you should feel bad about skipping tests in the early phase of a product. The code you write is either 1) likely to be thrown away soon, or 2) so >>
This was built into XML. You had to do <values><value>1</value>...</values>, and if need arose, you'd just extend it to <value meta="true">1</value>
I almost always regret using arrays of scalars in JSON APIs. Even if you think you need [1, 2, 3], you'll eventually realise that you need something like
[
{ "value": 1, "meta": true },
{ "value": 2, "meta": false },
{ "value": 3, "meta": true }
]
@anerdguynow Maybe you're referring to something else, but I'm getting *really* tired of the endless shameless engagement bait à la "Do you prefer tabs or spaces?"
@alexdotjs@ascorbic 90% of why SPAs are a thing is because you want to be able to navigate without having the whole page reload every time. Frames solved that but were considered "wrong"
@CFDevelop@azamsharp@dhh Randomly stumbled upon this tool today. Haven't tried it myself, but it sounds like something that would fit your testing workflow like a glove https://t.co/DEIAp9cJAS
@CFDevelop@azamsharp@dhh >> the unit testing purists nor the end-to-end enthusiasts, but I find it a very productive way to develop new functionality (I never need to run the app locally) and it enables the whole team to make changes with confidence
@CFDevelop@azamsharp@dhh Most of the test cases I write for a web backend project fall into one of the following two categories: put stuff in the DB and verify that an endpoint returns the right thing, or call an endpoint and verify there's the right stuff in the DB. Probably doesn't satisfy neither >>