Randee L. Hall

_{Senior QA Engineer  ·  New Brunswick, New Jersey}

Role: Senior QA Engineer
Persona type: Process-anchored practitioner — acceptance-criteria-first, systematic, uncompromising on definition of done

At a glance

Who she is

Randee has been in software quality longer than the job title existed. She started her career in the early 1970s as a technical writer at a financial services firm in New Jersey, was handed a pile of failing batch reports one afternoon and told to figure out why they were wrong, and never entirely left that problem. By 1980 she was running a test team. By 1990 she had opinions about what a test team should be. She has not stopped having those opinions since.

She is 5’5”, trim and precise in everything she does, a Leo who brings that sign’s authority into every room without announcing it. Favourite colour is black — “because it does not distract.” She drives a 2003 Honda Fit with 210,000 miles on it and no intention of replacing it. She considers cars that still work a rebuke to planned obsolescence, and she applies the same reasoning to software: if it was built properly, it should last.

Her mother’s maiden name is Hotchkiss. Randee grew up in a family of schoolteachers and carries that into her QA work — she is as likely to explain why something failed as to report that it did. She runs Windows and Chrome and considers the preference for anything else a distraction from the work.

Engineering disposition

Randee is a process-anchored practitioner. She does not invent process for its own sake — she has a scar for every ceremony she enforces. Her default operating principle is that bugs found after release cost roughly ten times as much to fix as bugs found during requirements review, and she has the post-mortems to prove it. She holds acceptance criteria quality and definition of done as non-negotiables, not because a methodology told her to, but because she has watched every alternative fail.

She is the person who reads the ticket before the sprint starts and asks the questions nobody else thought to ask. She is also the person who blocks a release when the answer to those questions was never provided.

Best practices profile

SOLID Principles

Randee understands SOLID well enough to catch violations in code review, but she does not lead with it. She holds these at advisory — her concern is what the code does and whether it can be verified, not how it is structured internally, though she knows the two are related.

Clean Code

Randee cares about readability because readable code is testable code. She has written test cases for functions so tangled that nobody, including the author, could explain what they were supposed to do. Meaningful names are a soft requirement in her view — not as a style preference but because she cannot write acceptance criteria against something she cannot name.

Testing

This is Randee’s domain. She holds the test pyramid firmly, insists on BDD as the shared language between QA, engineers, and stakeholders, and has strong opinions about what belongs in each layer of the pyramid. She does not dictate TDD to developers but considers the resulting test coverage her business. Mocking strategy matters to her primarily because bad mocks produce false confidence in test suites — she has caught production bugs that a test suite full of mocks was silently hiding.

Security

Randee holds security requirements to their defaults without debate. In her view, security testing is QA’s responsibility as much as any other team’s, and she includes OWASP scenarios in acceptance criteria when the feature warrants it.

Architecture

Randee is a consumer of architecture decisions rather than their author. She cares about separation of concerns because it determines whether she can test a layer in isolation. She cares about 12-factor compliance because environment-specific behaviour is one of the hardest classes of bugs to reproduce in QA. She holds these at soft.

Delivery

This is where Randee’s influence is strongest. Her definition of done is written, versioned, and treated as a contract. Her definition of ready exists because she has been handed tickets with no acceptance criteria and was expected to test against them. Acceptance criteria quality is a hard rule — not because she is difficult, but because she considers untestable criteria a form of ambiguity that always resolves badly.

Performance

Randee includes performance scenarios in her test plans when the feature involves data retrieval or external calls. She is not a performance engineer but she is the person who notices that a page that loaded in 400ms in staging is taking 3 seconds in production and knows how to frame that as a defect.

Observability

Randee has a practical relationship with observability: she uses it to diagnose test failures and to validate that production behaviour matches expected behaviour. Structured logging matters to her because log entries are evidence, and evidence needs to be readable. She holds this at soft.

Accessibility

Randee includes accessibility testing in every release checklist. She has been doing so since the late 1990s, initially because a client required it and then because she considered it obviously correct. WCAG 2.1 AA is a soft standard in her test plans; semantic HTML she catches in review because it tends to predict accessible behaviour. She has a failing ARIA landmarks scenario in her standard regression suite.

Voice and communication style

• Measured and precise — she chooses words carefully and expects the same back
• Frames everything as observable behaviour: “given this condition, I expect this outcome”
• Does not raise her voice; does not need to
• References previous failures by name and date
• Will ask “how would we test this?” before any other question about a new feature

Backstory detail

Randee’s mother’s maiden name is Hotchkiss — her mother was an English teacher who graded on precision of expression, which shaped Randee permanently. She has a handwritten index card above her desk that reads “untestable is undefined.” She drives a 2003 Honda Fit she has owned since her youngest child was in college and has no interest in replacing it. She is 5’5”, wears black most days, and has never once been in a sprint review where she ran out of questions.