Engineering's Ability: Software Testing


Description

The goal of testing is not 100% code coverage, but the appropriate amount of effort to ensure the least amount of value disruption for our clients and greater viability from the perspective of our client-facing teams (fewer "value-impeding" bugs = better experience for everyone).

This Ability is influenced by this article on the testing pyramid.

Milestone 1

(adds 1 mile to your journey)

I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to a squad when wielding this ability, and therefore I would put them in situations where they can employ this ability with only a small amount of guidance


  • Can write unit tests without much help
  • Can write integration tests with assistance
  • Aware of mocking/stubbing, but has not perfected when/where to use it
  • Aware of flake-causing issues, but misses them sometimes

Milestone 2

(adds 3 miles to your journey)

I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to a squad when wielding this ability, and therefore I would put them in situations where they can employ this ability, with no assistance as well as being a trusted active or passive mentor to others


  • Can write unit tests
  • Can write integration tests
  • Can do the above with mocks/stubs
  • Helps others write unit & integration tests
  • Writes end-to-end tests with assistance
  • Rarely introduces flakes

Milestone 3

(adds 6 miles to your journey)

I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to multiple squads when wielding this ability, and therefore I would put them in situations where they can employ this ability as well as being considered an expert within this discipline


  • Writes end-to-end tests
    • Actively improves how we write unit & integration tests
    • Helps others write end-to-end tests (knows when it is a good time to invest in this level and when it is not)
    • Known flake fixer
  • Is an example of how to mock/stub to ensure you are testing what you intended and keep the performance of the test suite

Milestone 4

(adds 12 miles to your journey)

I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to a squad when wielding this ability, and therefore I would put them in situations where they can not only employ this ability but where they set the tone for this at the company level


  • Look into new methods to proactively reduce flakes
  • Proactive; for example…
    • … in how we reduce flakes
    • … in how we approach test coverage
    • … in how we ???
  • Is seen as THE example for all test automation
  • Is continuously aware and up to date with new technologies, tools, and methodologies.

Milestone 5

(adds 20 miles to your journey)

I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to not just internal teams but the community/industry in general when wielding this ability, and they are recognized by the community/industry as an expert


  • Can create an automation framework from scratch.
  • Research, test, and integrate new technologies, tools, and methodologies.

Configuration Health

  • ✅ Associated with 4 roles
  • ⚠️ Has been referenced in no observations
  • ℹ️ Fewer than five people (1) achieved a milestone on this ability. To ensure anonymity, analysis will only appear after at least five people have milestones.
  • ⛔️ Last updated: about 2 years ago
  • ℹ️ Last conversed about: over 3 years ago

Role & Position Requirements

Examples / Observations

An observation relating to  Software Testing  has not been publicly recognized yet.

Conversations about Software Testing

This section is for CareerPlug folks only. Sign your team up to find your Gruuv!

Embed code

<iframe src="http://ourgruuv.com/our/powers/211?embed=true&name=software_testing&organization=careerplug"></iframe>