🚀 GUS Test Suite Automation Extension
A VS Code/Cursor extension for automating GUS Test Suite creation with AI-powered test scenario generation.
Note: Works with both VS Code and Cursor
✨ Key Features
- 🔗 Multi-repository support (GitCore, GitSoma, GitHub)
- 🤖 AI-powered test scenario generation from PR analysis
- 📦 Bulk processing for multiple work items
- 📄 Generate tests directly from file URLs
- 🔒 Secure authentication with GUS and Git tokens
- 🎯 Smart filtering by Epic, Release, or Date Range
- ✏️ Interactive editing before saving to GUS
Table of Contents
💾 Installation
With options 1 and 2, you will get automatic updates
VS Code: Install from VS Code Marketplace
Cursor: Install from Open VSX Registry
Manual Installation (Alternative):
- Download the
gustestsuiteautomation-1.0.9.vsix file
- Open Command Palette (
Cmd+Shift+P or Ctrl+Shift+P)
- Select "Extensions: Install from VSIX"
- Choose the downloaded file
🚀 Quick Start
- Install the extension (see above)
- Set up authentication (see below) - GUS and GIT
- Set up Claude token (see below)
- Open Command Palette → Enter "Gusify"
- Choose your option: Single PR, Bulk Work Items, or File URL
📝 How to Use
Option 1: Single PR Processing
- Command Palette → Enter "Gusify"
- Select option "Gusify Single PR"
- Paste your PR link (GitCore, GitSoma, or GitHub)
- Review AI-generated test scenarios
- Edit as needed
- Save to GUS
Option 2: Bulk Work Item Processing
- Command Palette → Enter "Gusify"
- Select option "Gusify My Work Items (Bulk)"
- Filter by Epic, Release, or Date Range (optional)
- Click "Gusify"
- Review test scenarios for all PRs
- Save to GUS
Features:
- Filter by Epic name or ID
- Filter by Release/Build (main and patch builds)
- Automatic PR discovery across all repositories
Option 3: File URL Processing
- Command Palette → Enter "Gusify"
- Select option "Gusify From File URL"
- Paste the complete file URL (including https://)
- Enter Work Item name (format: W-XXXXXXXX)
- Review and edit test scenarios
- Save to GUS
🔐 Authentication Setup
Git Access Tokens
You only need tokens for repositories you use. All tokens are stored securely.
How to get your token:
- Go to your Git platform:
- Click profile picture → Settings → Developer Settings
- Personal Access Token → Tokens (Classic) → Generate new token
- Give it a descriptive name
- Select scopes:
repo and read:org
- Click "Generate Token" and copy immediately
- Launch tool by opening Command Palette → Enter "Gusify"
- Go to Settings (4th option)
GUS Authentication
Choose one of three methods:
Method 1: Browser-Based Login (Recommended)
- Select "Login via Browser"
- Sign in GUS when browser opens and Allow
- Copy the complete URL and paste it into tool
Method 2: Standard Login
- Enter credentials:
- Username: gusdomainusername@gus.com (e.g., prateek.jha@gus.com)
- Password: Your SSO password
- Okta 2FA: 6-digit code from authenticator app
If authentication fails:
Method 3: Workbench Access Token
- Open Workbench for GUS org
- Login with Salesforce
- Open browser Dev Tools → Network tab
- Run any query
- Find the network call → Headers → Copy Bearer token from Authorization header
🔑 Set up Claude Token
- Command Palette → Enter "Gusify"
- Open Settings (4th option)
💡 Tips
- Always review AI-generated test scenarios before saving
- Add additional context and edge cases where needed
- Use descriptive names for test scenarios
- Group related tests under appropriate GUS themes
❓ Frequently Asked Questions (FAQ)
Q: What repositories are supported?
A: GitCore, GitSoma, and GitHub.
Q: Do I need tokens for all repositories?
A: No, only for the ones you use.
Q: Is my data secure?
A: Yes, all credentials are encrypted and stored securely in VS Code's secret storage.
Q: Can I edit generated test scenarios?
A: Yes, review and edit everything before saving to GUS.
Q: How are test scenarios generated?
A: AI analyzes your PR changes and generates relevant test scenarios automatically.
Q: What if I don't have a PR but want to generate tests?
A: Use "Gusify from File URL" to generate tests from any file in your repository.
Q: How long do tokens last?
A: Git tokens don't expire (unless you set one). GUS tokens expire after inactivity—just re-authenticate when prompted.
👨💻 Development
To modify or extend this extension:
- Clone the repository from GitSoma
- Run
npm install to install dependencies
- Make your changes to the TypeScript files in the
src/ directory
- Press F5 to start debugging in a new Extension Development Host window
- Use
vsce package to create a new VSIX file for distribution
Building the Extension
To compile the TypeScript source to JavaScript:
npm run compile
To package the extension into a VSIX file:
npx vsce package
🤝 Contributing
Contributions are welcome! Please follow these guidelines:
- Fork the repository
- Create a feature branch
- Make your changes with clear commit messages
- Test thoroughly
- Submit a pull request
Made with ❤️ by the Salesforce Alchemy Team