skills.rest
nandini-teqfocus avatar

nandini-teqfocus

Community

@nandini-teqfocus

0Followers
|
4Public Repos
|
2Published Skills

Nandini-teqfocus provides TestSprite skills for bootstrapping runnable test suites and verifying code changes against existing tests before completion.

🐙 GitHub ↗
Skills Distribution
DomainDeveloper To...Test Suite Bootstr.. (40%)Change Verificatio.. (40%)Failure Artifact I.. (20%)

Agent Skills by nandini-teqfocus

Showing 2 vetted skills indexed across 1 GitHub repositories.

nandini-teqfocusnandini-teqfocus

testsprite-onboard

Creates and smoke-runs a seed TestSprite test suite for repositories without existing tests.

Community
Advanced
nandini-teqfocusnandini-teqfocus

testsprite-verify

Runs TestSprite CLI tests against shipped code changes and reports terminal verdicts.

Community
Advanced

Frequently Asked Questions About nandini-teqfocus

FAQPage Schema
What tasks can I accomplish with nandini-teqfocus's TestSprite skills?▼

Two tasks: bootstrap a fresh repo with a complete TestSprite project, derived tests, and a smoke-run green verdict; and verify code changes by running relevant existing tests or newly created frontend plans and backend Python assertions to a terminal verdict.

Who should use the testsprite-onboard and testsprite-verify skills?▼

Developers working in TestSprite-tested repositories. Use testsprite-onboard when a repo has no TestSprite tests yet or right after `testsprite setup`; use testsprite-verify after finishing a feature or fix, before reporting the work as complete.

When should I use testsprite-onboard versus testsprite-verify?▼

Use testsprite-onboard only for first-run setup: a fresh project, immediately after `testsprite setup`, or when asked to bootstrap tests. Use testsprite-verify whenever code outside docs/config changed and needs verification against existing or newly created tests.

What are the prerequisites for using these TestSprite skills?▼

A repository with the `testsprite` CLI available. Onboarding requires a target URL and authentication to create the project; verification requires an existing TestSprite project with tests, or the ability to create a frontend plan or backend Python assertion for the change.

How does testsprite-verify confirm a change is complete?▼

It runs the relevant TestSprite tests covering the change via the `testsprite` CLI, inspects any failure artifacts produced, and only reports the work done once tests reach a passing terminal verdict. New tests are created if coverage is missing.