portfolio

I test com­plex sys­tems, build qual­i­ty prac­tices, and help teams think more clear­ly about risk.

Over the last ten years I’ve test­ed dis­trib­uted sys­tems across health­care, e‑commerce, bank­ing, and order ful­fill­ment, from iOS pri­va­cy apps to ware­house inte­gra­tions to mobile bank­ing plat­forms. My back­ground as a for­mer attor­ney shapes how I approach test­ing: I think in edge cas­es, test assump­tions, and look for the gaps between what a sys­tem is sup­posed to do and what it actu­al­ly does when things go wrong.

what I do

explorato­ry test­ing on com­plex sys­tems
I am the dis­cov­er­er of the bro­ken, find­ing the bugs that slip through auto­mat­ed checks because they require under­stand­ing how sys­tems actu­al­ly behave under real-world con­di­tions. Inte­gra­tion points, ful­fill­ment work­flows, APIs that inter­act in unex­pect­ed ways.

train­ing & cur­ricu­lum devel­op­ment
I’ve built test­ing cur­ric­u­la for devel­op­ers, cre­at­ed onboard­ing pro­grams for peo­ple new to tech, and trained teams on explorato­ry test­ing, risk analy­sis, and work­ing in con­text-dri­ven shops.

qual­i­ty lead­er­ship & com­mu­ni­ty build­ing
As QE Com­mu­ni­ty Lead at Seek­Well, I run com­mu­ni­ty meet­ings, pub­lish a biweek­ly newslet­ter, and work with a com­mit­tee to iden­ti­fy and stan­dard­ize good test­ing prac­tices across the orga­ni­za­tion.

testing philosophy

  • I believe we can­not test qual­i­ty in. By the time soft­ware reach­es us for test­ing, it’s too late if that’s the only place we’re involved. We get into design, refine­ment, and plan­ning, ask­ing the right ques­tions at the right time, because that’s where qual­i­ty actu­al­ly gets built.
  • I believe good qual­i­ty is a team effort. No sin­gle per­son or role can own it.
  • I believe we build bet­ter soft­ware when we think about peo­ple hav­ing a bad day and still hav­ing to use it, whether that’s acces­si­bil­i­ty con­cerns, cog­ni­tive load, or just reduc­ing rage clicks.
  • I believe automa­tion builds con­fi­dence that the things we knew about did­n’t break. It can­not tell you that the things you did­n’t know about did­n’t break. Explorato­ry test­ing and con­text-dri­ven test­ing will always have a place for exact­ly that rea­son.
  • I believe the prac­tices testers have built — risk think­ing, skep­ti­cism, ask­ing ‘but what could go wrong’ — will out­last what­ev­er AI does to the role itself. Testers are adap­tive crea­tures. What­ev­er you call us, we’ll keep doing what we’ve always done well. The least excit­ing part (to me!) was always just writ­ing the code.

tools & resources

test­ing resources — My curat­ed list of books, blogs, exer­cis­es, and com­mu­ni­ties I rec­om­mend
→ github.com/racheljoi/testing-resources

More tools, test exam­ples, and code com­ing soon. Cur­rent­ly work­ing on a Rav­el­ry inte­gra­tion and tests around that to show­case my skills.

skills

explorato­ry test­ing · inte­gra­tion test­ing · API test­ing · automa­tion strat­e­gy · risk analy­sis · sys­tems think­ing · cur­ricu­lum devel­op­ment · con­text-dri­ven test­ing · mobile test­ing (iOS/Android) · team lead­er­ship

Want to work togeth­er?
Con­nect with me on LinkedIn! I respond to mes­sages there.

Scroll to Top