testdriver:secrets

Manage passwords and secrets in TestDriver tests with secret: true.

238|34|Updated Aug 25, 2024
One-click install
npx skills add https://github.com/testdriverai/testdriverai --skill testdriver-secrets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testdriver:secrets
Source: https://github.com/testdriverai/testdriverai/tree/main/ai/skills/testdriver%3Asecrets
Command: npx skills add https://github.com/testdriverai/testdriverai --skill testdriver-secrets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Protect sensitive information like passwords, API keys, and tokens in your TestDriver tests.

Core Features & Use Cases

  • Typing secrets securely by using the secret: true option to prevent the value from being logged or stored.
  • Storing secrets in GitHub repository secrets or environment variables to keep credentials out of code.
  • Local development guidelines to avoid committing secrets and to use a .env file for local testing.

Quick Start

Run a secure test by typing sensitive data with secret: true to prevent exposure.

Frequently Asked Questions about testdriver:secrets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I securely type passwords and API keys in TestDriver tests?

Store secrets in GitHub repository secrets or environment variables to keep credentials out of code. For local development, use a .env file to manage environment variables and avoid committing secrets to version control.

What is the best way to manage credentials across local development and CI environments?

TestDriver supports credential handling across local development, CI, and cloud sandboxes. You can use environment variables or secret-storage practices to maintain consistent secret management throughout your testing workflows.

Does the secret typing feature work with environment variables in CI pipelines?

Yes, you can use the secret: true option with tokens and API keys. This prevents sensitive values from being logged or stored during test execution, protecting credentials across all testing flows.

Why should I avoid hardcoding secrets in my test scripts?

Without secure secret handling, credentials may be logged or stored during test execution. Using the secret: true option prevents value exposure, ensuring passwords and API keys remain protected throughout the testing process.