How do I install the Rondleysg QA Agents Wdio Skill QA Wdio Add New Test skill?

Run npx skillmds@latest add tomevault-io/rondleysg-qa-agents-wdio-skill-qa-wdio-add-new-test in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Rondleysg QA Agents Wdio Skill QA Wdio Add New Test safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Rondleysg QA Agents Wdio Skill QA Wdio Add New Test?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Rondleysg QA Agents Wdio Skill QA Wdio Add New Test free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Rondleysg QA Agents Wdio Skill QA Wdio Add New Test?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Rondleysg QA Agents Wdio Skill QA Wdio Add New Test by tomevault-io

Name: Rondleysg QA Agents Wdio Skill QA Wdio Add New Test
Author: tomevault-io

File contents

Add new test (E2E WebdriverIO)

Ao adicionar um novo teste ao projeto E2E em tests/e2e/, seguir estas convenções.

Localização

Arquivo em tests/e2e/specs/ (na subpasta do fluxo, se houver), com sufixo .spec.ts.

Imports

Sempre relativos a partir do spec (ex.: ../../data/Constants, ../../screenobjects/HomeScreen, ../../helpers/Utils).
Nunca importar @playwright/test ou APIs Playwright.

Estrutura do teste

Runner: Mocha — describe, it, before, after.
Device/Browser: Usar getDeviceFromCapabilities('deviceA') ou getDeviceFromCapabilities('browserA') conforme o config (helpers/Utils.ts).
Screenobjects: Usar métodos dos screenobjects para interações (ex.: HomeScreen.waitForIsShown(), CartScreen.tapOnAddButton()).
Data: Usar constantes de data/Constants.ts ou data/Logins.ts (ex.: PLACE_NAME_TO_TEST, LOGINS_TO_TEST) em vez de valores fixos quando fizer sentido.
Seletores: Via helpers getElementByTestID, getElementByText, getElementByAccessibilityLabel (Utils.ts) ou dentro de screenobjects.
Assertions: expect (Mocha/Chai); aguardar com waitForDisplayed, waitForExist quando necessário. Ex.: expect(element).toBeDisplayed(), expect(value).toEqual(expected).
Arrange-Act-Assert: Estrutura clara; nome do teste descritivo (cenário + resultado esperado).
Async: Todas as interações e assertions assíncronas com async/await.

Allure (opcional)

Se o projeto usar @wdio/allure-reporter, seguir o padrão dos specs existentes (ex.: allureReporter.addFeature, allureReporter.startStep/endStep).

Checklist

Arquivo em tests/e2e/specs/ com sufixo .spec.ts
Imports relativos (data, screenobjects, helpers)
Uso de data/ quando há dados reutilizáveis
Nome do teste descreve cenário e resultado esperado
Async/await usado de forma consistente

References

Exemplos: tests/e2e/specs/basic-features.spec.ts, tests/e2e/specs/cart/checkout-cart.spec.ts
Helpers: tests/e2e/helpers/Utils.ts

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: rondleysg-qa-agents-wdio-skill-qa-wdio-add-new-testdescription: Add new test (E2E WebdriverIO)---# Add new test (E2E WebdriverIO)Ao adicionar um novo teste ao projeto E2E em **__tests__/e2e/**, seguir estas convenções.## Localização- Arquivo em **__tests__/e2e/specs/** (na subpasta do fluxo, se houver), com sufixo **.spec.ts**.## Imports- Sempre **relativos** a partir do spec (ex.: `../../data/Constants`, `../../screenobjects/HomeScreen`, `../../helpers/Utils`).- Nunca importar `@playwright/test` ou APIs Playwright.## Estrutura do teste- **Runner:** Mocha — `describe`, `it`, `before`, `after`.- **Device/Browser:** Usar `getDeviceFromCapabilities('deviceA')` ou `getDeviceFromCapabilities('browserA')` conforme o config (helpers/Utils.ts).- **Screenobjects:** Usar métodos dos screenobjects para interações (ex.: `HomeScreen.waitForIsShown()`, `CartScreen.tapOnAddButton()`).- **Data:** Usar constantes de **data/Constants.ts** ou **data/Logins.ts** (ex.: `PLACE_NAME_TO_TEST`, `LOGINS_TO_TEST`) em vez de valores fixos quando fizer sentido.- **Seletores:** Via helpers `getElementByTestID`, `getElementByText`, `getElementByAccessibilityLabel` (Utils.ts) ou dentro de screenobjects.- **Assertions:** `expect` (Mocha/Chai); aguardar com `waitForDisplayed`, `waitForExist` quando necessário. Ex.: `expect(element).toBeDisplayed()`, `expect(value).toEqual(expected)`.- **Arrange-Act-Assert:** Estrutura clara; nome do teste descritivo (cenário + resultado esperado).- **Async:** Todas as interações e assertions assíncronas com async/await.## Allure (opcional)Se o projeto usar `@wdio/allure-reporter`, seguir o padrão dos specs existentes (ex.: `allureReporter.addFeature`, `allureReporter.startStep`/`endStep`).## Checklist- [ ] Arquivo em __tests__/e2e/specs/ com sufixo .spec.ts- [ ] Imports relativos (data, screenobjects, helpers)- [ ] Uso de data/ quando há dados reutilizáveis- [ ] Nome do teste descreve cenário e resultado esperado- [ ] Async/await usado de forma consistente## References- Exemplos: __tests__/e2e/specs/basic-features.spec.ts, __tests__/e2e/specs/cart/checkout-cart.spec.ts- Helpers: __tests__/e2e/helpers/Utils.ts---> Converted and distributed by [TomeVault](https://tomevault.io/claim/rondleysg) — claim your Tome and manage your conversions.

Frequently asked questions

Rondleysg QA Agents Wdio Skill QA Wdio Add New Test