APhoenixRises

I sometimes use the generator to get an idea of what selectors I might want to use and then extract the relevant bits to page objects. The risk is that not everyone knows that recorded tests are a starting point and not the destination.

No joke, but this is exactly my situation.

This is a larger blow to smaller universities like UTSA and UTD that finally have budding research programs. I really wish the Texas government would stay out of people's lives. This is just another bill in the long line of bills this year intended to kill "wokeness". Our government doesn't give a single care about education. As long as they think they can get conforming, uninformed youth out of something, they'll do anything.

How does Step CI handle testing business logic? I don't see how anything other than input/boundary testing could be generated automatically.

I like to keep one of my personal laptops running Linux, but I won't be using one at work again soon unless I have the rights to pave and reinstall. While I'm more than willing to spend my evenings tinkering issues on my own laptop, I can't spend hours of work time debugging a graphics or audio issue that pops up.

I had a Zephyrus G15 (2021) which ran great, but the screen brightness wasn't great. When I heard this year's G14 had a brighter display and an AMD CPU and GPU, I dove in and installed Fedora. Other than standby, everything just worked.

The thing I will ding Asus about is serviceability. It's easy enough to remove the screws to take the bottom panel off, but there was always one screw for NVME/Wifi that had so much loctite that I ended up needing a special pair of plyers to remove.

Far too many

- Thinkpad workstation laptop provided by work

- One desktop running Windows 11 (gaming/development)

- One laptop dual booting Windows 11 and Fedora (gaming/development)

- Surface Laptop Studio running Windows 11 (content consumption, light development)

- Surface Pro X (previous content consumption device. I'll sell it "someday")

- Samsung Galaxy Tab 7+ (mobile gaming, content consumption)

I also compulsively switch out my laptops/tablets on a yearly basis...I have a problem.

Granted everyone's case is different, but my doctor went forward with medications only as part of a comprehensive plan to deal with my mental health which included seeing a therapist and committing to an exercise program (it sounded silly to be before, but exercise can be for some people can be nature's antidepressant). I'm on a 6 week to 3-month schedule of follow-up visits with my doctor to keep track of where I'm at mentally. Yes, there are absolutely doctors out there that will toss pills to people and send them on their way, but I don't think it's the majority. I also vet doctors the same way I would a mechanic or anyone else who is going to be doing important work for me. It can be hard, but there are doctors who care about doing the right thing out there.

There are risks with taking any medication, so your concerns have merit. I take medications for depression, anxiety, and ADHD. I consider myself very lucky to have a very patient and supportive doctor. As I come on and off medications, we always talk about the risks and potential benefits. The choice that I have to make for myself is if the benefits outweigh the risks.

Another thing to consider is that while medications can improve your quality of life, they're only part of the solution. I see a therapist weekly and a coach for ADHD on and off throughout the year. I have to exercise regularly or else my anxiety and depression become unbearable. It's hard work, but I know that consequences of not doing those things are far worse. In my case, my medications don't solve my depression and anxiety. What they do is bring me up enough that I can keep moving forward and keep improving, with the hope that one day I will untangle the mess of emotions and I may not need them anymore.

You mentioned that you've tried therapy. Did you stop because you felt better or because you didn't have a good rapport with your therapist? This is just my experience, but it took 2-3 years before my therapist and I were able to tear down all of the defenses I put up for decades. I'm at year 7 and I'm finally starting to push through some of my own behaviors and stories I tell myself to make progress and take back control of parts of my life I thought I had no control over.

I can't tell you what you should do. What I will say with absolutely certainty is that it is not weakness to want help. It is not weak to want to live a productive life. I would talk to your doctor about what you're experiencing to have another opinion about your situation. Medication for some people is the complete answer, but that's not always the case. I would strongly encourage you to find a therapist that you have a good rapport with and stay with them. Once again, at least in my case, the medications balanced me enough to deal with my mental health issues. Dealing with depression takes a lot of time and energy, but now I know the issues I'm really fighting, I don't feel helpless anymore. Take care of yourself. You are worthy of having a good life.

In an ideal world, devs would always have the time to test their own code. The unit and integration bits aren't the pain point, but once you reach the API or UI, people's knowledge varies widely. That's where a good QE org, either embedded or a mix of centralized and embedded, can be very helpful. In my past companies we've pushed to be champions or domain experts in test automation who's main purpose is to make testing for everyone else suck less. Sure, you will definitely take the brunt of test automation tasks, but some of those tasks should be targeted towards removing impediments for testing.

In one situation I ran into a team who was very frustrated with their automation because it was so slow. After a bit of investigation, I found out they were setting up all of their test data through database migrations, which were 10+ minutes slow. I asked why they weren't using the API to setup test data, to which they replied that none of them had experience with the API. After hacking away it in my spare time for a few weeks, I had a perfectly functional API client, and the tests were converted over time out of using the migrations.

I saw this the other day, and while it might sound cheesy, but someone said that QA to them was "quality acceleration", which actually fits fairly well. I have never worked at a company who had enough testers to go around. Keeping a smaller group of centralized testers to handle the really tough technical challenges, and a larger group of embedded testers who evangelize on testing practices was the most successful approach.

In this case, I wouldn't say you absolutely need a full quality team, but having some folks whose primary focus is testing and test automation to help skill up your dev teams sounds reasonable.

My assumption was that it was a branch of functionality that could be dropped to make any maintenance of classic Edge easier. I was really irritated when they dropped support as epub support for Windows has been minimal until recently.

For my first stab at learning something new I usually try on my own, but when I'm getting lost or things aren't working as expected I like videos, especially ones that weren't prerecorded. The number of times documentation either takes a mental leap or actually skips a step can be frustrating. It's also helpful to see where someone else makes mistakes because it's often the ones I would've made also.

What's missing from the title of these articles is "to me" or "in the context of my project". The approach to testing a CRUD/line of business app is tested is different than the approach for testing something like EC2, which is also different than how a library/package is tested. Without context, it's really easy to argue exceptions or counter-examples to any opinion.

You definitely have some strong opinions about testing. I'd suggest being more specific so your guidance is more clear. "people who test what they think is appropriate" is really subjective and makes it seem like there's two camps: people who "get" the author's perspective, and those who don't. I've tried the "do" and "don't do" approach, but that's not enough information usually. Teach by examples. Lots of examples. Calling things BS isn't going to change someone's mind. I'd also re-enforce that these practices are for your codebase. Every project is different and has different challenges. There's a reasonable counter-example for each item in your TLDR, and "unless you deem fit" doesn't feel like it gives developers leeway given how strongly you state your opinions.