John’s HeedBase Adventure 🚀
Meet John, a busy developer who just launched his online bookstore. He’s worried: “What if customers can’t log in? What if the checkout breaks? How do I make sure everything works?”
Then he discovered HeedBase. Let’s follow his journey from worried developer to confident website owner in just 5 minutes!
Chapter 1: The Beginning 📝
John heard about HeedBase from a friend and decided to give it a try. He went to app.heedbase.com and signed up with his email.
“This looks simple enough,” John thought as he clicked “Sign Up” and entered his details.
After verifying his email, John found himself on a clean dashboard. “No overwhelming interface, just a simple ‘New Project’ button. I like this already.”
Chapter 2: The Magic Discovery 🔍
John clicked “New Project” and entered his bookstore details:
- Project name: “My Bookstore Tests”
- Website URL:
https://mybookstore.com - Description: “Testing book search, cart, and checkout”
“Now what?” John wondered.
But something amazing happened! HeedBase started exploring his website automatically. In the background, it was finding all the important elements:
- Login button:
button[data-testid="login-btn"] - Search input:
input[name="search"] - Cart icon:
.cart-icon - Book cards:
.book-item
“Wow,” John said, “it’s like having a detective that automatically maps out my entire website!”
Chapter 3: The Conversation 💬
Once the discovery was complete, John saw a chat interface. “This is where the magic happens,” he thought.
John typed: “Create a test for when someone buys a book”
HeedBase didn’t ask a million questions. Instead, it created two smart test scenarios:
Scenario 1: The Happy Path
- Given: A customer is browsing the bookstore
- When: They find a book they love and add it to cart
- Then: The book appears in their cart and they can checkout
Scenario 2: The Oops Moment
- Given: A customer wants a book that’s out of stock
- When: They try to add it to cart
- Then: They see a friendly “Sorry, sold out!” message
“This is incredible,” John said. “It thinks of both the good and bad scenarios automatically!”
Chapter 4: The Code Generation ✨
John clicked “Generate” on the first scenario, and HeedBase started working. “This is exciting,” he thought.
First, it gave him human-readable steps:
- Go to the bookstore homepage
- Click on a book
- Click “Add to Cart”
- Make sure it appears in the cart
- Click “Proceed to Checkout”
Then it created the actual Playwright code:
test('Successful book purchase', async ({ page }) => {
await page.goto('https://mybookstore.com');
await page.click('.book-item:first-child');
await page.click('button:has-text("Add to Cart")');
await expect(page.locator('.cart-item')).toBeVisible();
await page.click('button:has-text("Checkout")');
});While creating this code, HeedBase discovered even more elements - like a mushroom picker in a forest, gathering new selectors as it explored!
Chapter 5: The Reality Check 🛠️
John excitedly ran his first test, but it only partially worked! “Hmm, that’s interesting,” he thought.
Test Results:
- ✅ Book A purchase: PASSED (1.2s)
- ❌ Book B purchase: FAILED - Element not found (0.8s)
The test successfully added Book A to the cart, but couldn’t find Book B. “I guess HeedBase only found one book selector,” John realized.
But John didn’t worry. He opened the Selectors tab and saw all the elements HeedBase had discovered. There it was: .book-b-selector for Book B!
“This is easy,” John said. He copied the selector and added one line to his test:
// John added this line manually:
await page.click('.book-b-selector');“That took literally 10 seconds,” John said. “I can see all the selectors HeedBase found, so I can easily add whatever I need!”
Chapter 6: The Victory Moment 🎉
John ran his updated test and saw complete success:
Test Results:
- ✅ Book A purchase: PASSED (1.2s)
- ✅ Book B purchase: PASSED (1.1s)
- ✅ Out of stock scenario: PASSED (1.8s)
- 📊 Bonus: 5 new selectors discovered during testing
“I can’t believe it,” John said. “It took literally 10 seconds to fix, and now I have working tests that prove my website works perfectly!”
Chapter 7: The Bonus Adventure 📚
John was so excited that he decided to test his friend’s coffee shop website too!
The Challenge: “What if customers can’t order coffee online?”
John’s Solution:
- He created a project for coffeeshop.com
- HeedBase automatically found: Order button, Menu items, Checkout form
- John said: “Test ordering a cappuccino”
- HeedBase created a test that:
- Goes to the coffee shop
- Clicks “Cappuccino”
- Clicks “Add to Cart”
- Fills in delivery address
- Clicks “Order Now”
- Checks that order confirmation appears
The Happy Ending: John’s friend now knows her coffee ordering works perfectly, and customers will never be disappointed!
John’s Key Takeaways 💡
After his HeedBase adventure, John learned that:
- No technical knowledge needed - Just describe what you want to test
- Automatic discovery - HeedBase finds all the important elements
- Smart test creation - It thinks of both success and failure scenarios
- Real code generation - Get working Playwright tests (with easy manual fixes)
- Continuous learning - HeedBase discovers more elements as it works
- Easy troubleshooting - Use the Selectors tab to find and add missing elements
“This is exactly what I needed,” John said. “It’s not magic, but it’s way easier than writing tests from scratch. I can focus on building my business instead of worrying about testing!”
Common Issues & Solutions
❌ “Website not accessible”
- Ensure your website is publicly accessible (no authentication required)
- Check if the URL is correct and the site is online
❌ “No elements discovered”
- Wait 2-3 minutes for discovery to complete
- Try refreshing the project page
❌ “Tests failing”
- Check if your website structure changed
- Use the AI chat to update selectors: “Update the login button selector”
❌ “Can’t generate tests”
- Make sure you have at least one test case created
- Try creating a simpler test case first
Next steps
Need help? Reach us at support@heedbase.com.