@GregPaciga profile picture
@greg@tech.lgbt @GregPaciga

Lead developer in #DevOps and #Testing. Astrophysicist by training. Often curler, rower, cycler, and baker too. He/him. 🇨🇦🏳️‍🌈

Joined August 2010
  • Tweets 1,231
  • Following 163
  • Followers 226
110 Photos and videos
Pinned Tweet
@greg@tech.lgbt@GregPaciga
6 Nov 2022
For those switching over to #Mastodon find me here: @greg@tech.lgbt 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.
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 😞
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.
@greg@tech.lgbt retweeted
Forrest Brazeal
@forrestbrazeal
4 Oct 2022
new little song: "The Re-Org Rag (I'm My Own VP)"
2:18
219
2,639
10,174
@greg@tech.lgbt retweeted
Tina Fletcher@fletchertinam
28 Sep 2022
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
1
2
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.
@greg@tech.lgbt retweeted
🔎Julia Evans🔍
@b0rk
14 Sep 2022
a debugging manifesto
a debugging manifesto 1. inspect, don't squash try to fix the bug (crossed out) understand what happened (yes, smiley faces and stars) 2. check your assumptions person (thinking): "wait, how do I know that's true?" 3. being stuck is temporary person (thinking): "I will never figure this out!" ... 2 minutes later.... person (thinking): "well, I haven't tried X..." 4. don't go it alone person (speaking to other person): "hey, have you seen this problem before?" 5. trust nobody and nothing person (thinking): this library can't be buggy... OR CAN IT??? 6. there's always a reason computer: "computers are always logical, even when it doesn't feel that way" 7. build your toolkit person (holding toolkit): "wow, the CSS inspector makes debugging SO MUCH EASIER" 8. it can be an adventure person (talking, with cute bug next to them): "you wouldn't BELIEVE the weird bug I found" by @b0rk @omarieclaire, more like this at https://wizardzines.com

ALT a debugging manifesto 1. inspect, don't squash try to fix the bug (crossed out) understand what happened (yes, smiley faces and stars) 2. check your assumptions person (thinking): "wait, how do I know that's true?" 3. being stuck is temporary person (thinking): "I will never figure this out!" ... 2 minutes later.... person (thinking): "well, I haven't tried X..." 4. don't go it alone person (speaking to other person): "hey, have you seen this problem before?" 5. trust nobody and nothing person (thinking): this library can't be buggy... OR CAN IT??? 6. there's always a reason computer: "computers are always logical, even when it doesn't feel that way" 7. build your toolkit person (holding toolkit): "wow, the CSS inspector makes debugging SO MUCH EASIER" 8. it can be an adventure person (talking, with cute bug next to them): "you wouldn't BELIEVE the weird bug I found" by @b0rk @omarieclaire, more like this at https://wizardzines.com

87
1,818
6,766
Pro tip: Don't plagiarize your resume.
"We can't trust devs to test or produce quality code!" "Do you know their names?" "..." "Maybe start there."
We just installed our first ever "smart" light switch. It turns on by itself. Wondering if it automatically connected to someone else's house, and if so, what Morse code message should I try sending to them
Apparently hot take: CSS locators are better than xpaths. Why? Because your devs already know CSS.
People are really out here only writing test automation after features are already deployed eh? Wild
1
1
@greg@tech.lgbt retweeted
KWSQA@KWSQA
11 Jul 2022
We're so excited to welcome our speakers to #TQ2022: @AGareev @dsynadinos @offbeattesting @glennanderson @GregPaciga @thechainmailguy @larissar @MazinInaad @Revelzen @sergiocoltest @TheyWrestleTest @FionaCCharles @g33klady Visit kwsqa.org/tq2022/schedule/pr… for their session info!

2
10
15
Most of this thread works for any job, including #SoftwareTesting. I'm constantly surprised at how many people don't ask any questions in interviews, especially for a job that is all about asking questions.
Aakash Gupta
@aakashgupta
9 Jul 2022
Every PM interview ends with “what questions do you have for me?” 95% of applicants don’t impress. Their questions demonstrate lack of curiosity, and they ask too few. I’ve interviewed over 100 PMs over the last few months. Here’s how some ROCK this part of the interview:
@greg@tech.lgbt retweeted
Jurgen Appelo
@jurgenappelo
8 Jul 2022
I'm not a fan of canceling people. But that doesn't mean I want to be friends with them. This was worth writing.
26
69
508
@greg@tech.lgbt retweeted
eokulik@t34chmehowto
29 Jun 2022
You can often hear that testing is boring. And I agree - bad testing is boring. But good testing is fun, interesting and challenging.
7
23
116
@greg@tech.lgbt retweeted
Kent Beck 🌻
@KentBeck
16 Jun 2022
Here is where the Kingman Formula butts in. The Kingman Formula (look it up or take the queueing theory workshop I'm putting together) says that as the utilization approaches 100%, the wait time for new parts entering the system approaches infinity. Yep, *that* infinity.
7
12
71
Load more