The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
AI-Augmented Test Development Workflow
AI-Augmented Test Development Workflow
AI-Augmented SDET Workflow | Cursor + Git + Playwright
This project demonstrates how I integrate AI coding tools into a disciplined software testing workflow rather than relying on AI-generated code blindly.
The process starts with...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Trending
retrofuturism
Share your favorite designs from the past exploring the distant future. Or your own take on the aesthetic 🚀
halftone
Dots. Texture. Grain. Let's see your designs using the halftone technique.
Midjourney
Creatives are showing off what they're making with Midjourney.
colorgrade
Video editors sound off: How do you enhance the mood of your video in color grading?
Related posts
Deepen | Contra & Bubble.io Challenge
Say goodbye to boring small talk! 👋
Here is Deepen — a mobile card game for deeper connections, built completely on @Bubble.io . I created dynamic question decks and smooth workflows to make hangouts with friends effortless and fun.
https://www.youtube.com/watch?v=dAyuz8q9V6c
#BubbleFFA #NoCode #Bubble #Contra
Amazing, wish you win this challenge.
The Creative Edge panel with Cursor, Flora, and Contra Labs
Great to see
I recently built this workflow in n8n to automate the first stage of handling customer support requests.
The idea was to take an incoming ticket and let the system handle the repetitive work:
→ Receive the customer request through a webhook
→ Process and structure the incoming data
→ Use an AI Agent to understand the ticket
→ Classify it as Genuine, Spam, or Unclear
→ Route it based on the classification
→ Trigger the appropriate email action
→ Log the interaction in Google Sheets
I also added an Unclear path so that tickets the AI isn’t confident about don’t get blindly processed.
The goal isn’t to remove humans from customer support.
It’s to reduce the repetitive sorting and routing work, so the team can spend more time on the requests that actually need their attention.
Would you automate customer support differently? I’d love to hear how you’d approach it.
The Unclear lane is exactly the right guardrail. I’d add two production checks: redact PII before sending ticket text to the model, and measure false-positive/false-negative rates by category rather than a single accuracy score. Logging resolutions and human overrides back into...