tl;dr: Rippling does not ensure HSA contributions from your paycheck and deposits into the HSA actually match, leading to a situation where you may have money withheld from your paycheck that doesn’t actually get deposited into your HSA. If you use Rippling and have an HSA, you should really go audit your contributions and make sure they match the deposits into your HSA account. In my case, I was missing $400.
It's not so much about the environment itself, but the data in it. If the data you use for your tests is all hand crafted/manually created by someone who has left the company then you don't have any way to scale it (e.g. if you want to run a bunch of your tests in parallel and they may modify that data), or to make changes to address new functionality in your application, then your qa process will suffer immensely.
I wish people would think about the data they use for the tests a bit more, and how they can create it from scratch in a consistent and scalable way, that way they can always be testing against a clean environment with a known setup and avoid doing a bunch of bad things (like creating data on the fly as part of a test)
I've been in the QA space for a while now, and one thing that repeatedly comes up is people neglecting their QA data. It's always an afterthought about how to get their application into the right state to be able to test their functionality properly.
So I'm curious, how do you all manage the seeded test data that you need for your QA tests?
This[1] is something I've come across but not had a chance to play with, designed for reading non-smart meters that might work for you. I'm not sure if there's any way to run it on an old phone though.