📋
QASpace-CaseStudies
  • Home
  • Test Strategy
    • Vision of Quality
      • Good Test Coverage
      • ISO 29119 Certification
      • Date Internationalization Format
      • Localization Testing
      • Test Management
      • Creating TestCase
  • How to Test
    • How to write good TestCase?
      • Tips on Testing
      • Pair Testing
      • UserStory to TestCases
      • Optimising the development flow in a Scrum team
      • Rate/Prioritise bug tickets
  • Exploratory Testing
    • Exploratory Testing
      • Creating Test Charters
      • Test Charters
      • Velocity was too high
  • Agile
    • Implementing Scrumban
      • Breakdown Task
      • Common work across teams
      • Sustainable QA process in the organization
  • Philosophy of Testing
    • Brainstorming
  • Metrics
    • Risk Analysis
      • Testing Outsource
      • How to measure Quality?
  • Automation
    • AI-Automation
      • Software through the lens of AI
      • SAP/Salesforce Automation
      • Mobile Automation
      • Solve by automating the GUI?
      • Improve Skill-sets
      • Coding Skills
      • Working in BDD
      • Value of Test Automation
      • UI/API automation asset
      • TDD VS BDD
      • Selenium vs Cypress
      • An important consideration of Test Automation journey
      • Balance Test Automation Development
      • Automation is no longer providing value
      • Define AI in test automation
      • Unique Locators
      • Best Practices as QA, QA Lead, and Automation Engineer
      • Making friends with Imposters
  • Survey/Polls
    • Is QA really a Gatekeeper?
  • Performance
    • Performance Testing
      • Client-Side Performace
Powered by GitBook
On this page

Was this helpful?

  1. Automation
  2. AI-Automation

Improve Skill-sets

Case Study:

I’m a Qa Eng focusing on automation, looking to improve my personal-professional skill-sets, wondering if there are people who are or who know of others that fill roles like coach, mentor etc, something of a career coach/mentor but with more of an emphasis on creating a program of self study, one that may lead somewhere specifically but may also leave options open.

Recommendation 1:

This is a broad topic and so much of teaching and learning depends on the individuals involved. In broad strokes, here's the path that I set before new SDETs on my team (as their leader/coach):

  1. Take the time to learn the tools and technologies you'll be using. Our shop uses a lot of Python and HTTP, so everyone gets a basic language course plus a tour of RFC 7231.

  2. Learn good software development practices. Everyone works through The RSpec Book in which all the examples are Ruby. I leverage this to reinforce the language fundamentals by asking my charges to translate them to Python (and Behave/unittest instead of Cucumber/RSpec).

  3. Build a community of excellence. We practice pair and mob programming as well as code reviews where we discuss decisions, consequences, and alternatives.

  4. Aim higher. After The RSpec Book, advance to Uncle Bob's Clean Code and then Clean Architecture.

Note how little of this is focused on a particular set of technologies or tools. This fits into your "leave options open" requirement which I fully endorse. Technologies come and go. Principles and practices endure much longer.

I'll also note an oddity in our practice. We model developer-in-test as a specialized developer, not as an advanced tester as most shops do. I believe very strongly that this approach is superior and would be delighted to defend it. Oh, another book that I push is the venerable xUnit Test Patterns by Gerard Meszaros.

The Rspec Book is a trojan horse. It's ostensibly about RSpec but it's actually about software craftsmanship.

-- Mike Duskis

PreviousSolve by automating the GUI?NextCoding Skills

Last updated 4 years ago

Was this helpful?