📋
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

UI/API automation asset

Question:

I’m curious to learn how we can make UI/API automation everybody’s asset? Usually, automation developers are the only ones responsible for creating more coverage and there will always be a gap as long as the ratio between the number of product developers and automation developers is not equal. In this case, maybe we should involve product developers in this automation effort?

Insights:

There are two aspects of this question: more involvement of developers in QA and involvement specifically in API automation.

The first aspect depends highly on each company and luckily I'm seeing more companies investing on it. That said, I've been in situations where the developers came from companies in which they have a strong separation between the roles and they are harder to convince for a change. The way I managed to do this was by asking them for help on difficult challenges and getting interested in their job too (without bothering them).

For the second aspect, Devs writing tests for UI/API, I would highly recommend to check firstly their unit test. And maybe get some tool to check code coverage from their side... I've seen a lot of repetition of tests across disciplines.

-- Noemi Ferrera

PreviousValue of Test AutomationNextTDD VS BDD

Last updated 4 years ago

Was this helpful?