For those switching over to #Mastodon find me here: @[email protected]
I don't use twitter much but it's good to see what the testing hive mind is up to. I'm hoping I can find the same over there.
@sshsergey@ragunathjawahar@AdamTornhill Yes @ragunathjawahar is right. Tests also suffer from being too verbose. What I removed was a lot of over-engineered and unused code, as a prelude to other refactoring/redesign efforts, to remove that extra cost and liability.
I built a desktop back in 2013 and it survived 3 trips on moving trucks, but today carrying it from one room to another seems to have been the last straw. Aside from some loud fans it won't turn on at all π
@BeardedTesterUK I think it's friendlier for anything code-related, e.g. installing packages and using a terminal. That might just be because I'm much more used to it, but it's a big advantage to be on the same platform as the developers on my team (and dev teams are usually on mac)
If you do #TestAutomation in Toronto, I'm hiring 2 QA Engineers! One in #API testing a financial microservice system (java/spring), another doing #WebdriverIO UI + API (nextjs/typescript). Hybrid downtown. DMs are open.
Cool insights from @GregPaciga's #TQ2022 talk:
- All of his team's "flaky" automated tests could be fixed by making improvements to the application itself
- How a team approaches testing defines how agile they really are
It seems like in the last 6 months all my banks updated their sites to SPAs that share the same 2 bugs: (1) require a refresh after logging in to display anything and (2) fail to update balances after doing transactions.
If you're a QA doing UI testing, please do yourself (and me) a favour: learn a JavaScript framework and ditch Java. I don't care which one, honestly, but speaking the same language as devs is one of the best things you can do.