EnableEdge

299 posts

EnableEdge banner
EnableEdge

EnableEdge

@EnableEdge

40% faster releases, 30% lower QA spend, see ROI in a days with AI testing. Ready to solve your QA challenges? Book a free call

India 加入时间 Şubat 2025
86 关注17 粉丝
置顶推文
EnableEdge
EnableEdge@EnableEdge·
🚀 Mumbai Devs & Founders! Get a FREE QA Fast-Track Audit (₹15,000 value) for your app or website. Only 5 slots! Improve your quality fast. ✅ Follow @EnableEdge ✅🔁 this tweet Tag someone building apps/websites ⏳ 48 hours only! #MumbaiTech #QA #AppTesting #Trending #DevLife
EnableEdge tweet media
English
0
0
0
364
Marshall
Marshall@mdnlabs·
Drop your landing page 👇 Go roast another 🔥 Be kind... ish (no seriously, be nice)
English
279
2
134
13.4K
Sergio | QA for Web & Apps
Sergio | QA for Web & Apps@Jsergioding·
Unpopular opinion: If you only test on desktop, you didn't test at all. 40% of users are on mobile. Your app breaks on mobile Safari or MetaMask browser = you blocked 40% of revenue. "Works on my MacBook" isn't QA. Test where users actually are.
English
2
0
2
71
EnableEdge
EnableEdge@EnableEdge·
Day 12 of building my Playwright framework in public 🚀 Visual Regression Testing - Catching UI Bugs Before Users Do youtu.be/el2b-k7g_aE
YouTube video
YouTube
English
0
0
1
44
EnableEdge
EnableEdge@EnableEdge·
Day 11 of building my Playwright framework in public 🚀 Authentication Patterns - Login Once, Test Forever [youtu.be/Zh4ZMrtU3S4]
YouTube video
YouTube
English
0
0
1
29
EnableEdge
EnableEdge@EnableEdge·
Yesterday we used Claude to: ⚡ Generate test data instantly ✅ Create regex edge cases 🛠️ Build a Chrome extension after missing a bug AI isn't replacing testers. It's making us better. enableedge.com/blog/stop-worr…
English
0
0
2
58
EnableEdge
EnableEdge@EnableEdge·
@fundootesters Sabse jayeda use hone waala toh hai hi nahi. Meri machine pe chal raha hai, tumhara laptop kharab hai
हिन्दी
1
0
0
6
EnableEdge 已转推
Reuben Dickson
Reuben Dickson@reuben_dicksonE·
A team deploys a new update. Everything looks fine in testing. Minutes later, production breaks. Now the question is not “Who caused the bug?” The question is “Why didn’t we catch this earlier?” This is where QA (Quality Assurance) and DevOps intersect. Modern software is not released once. It is deployed daily, weekly, sometimes multiple times a day. Manual testing alone cannot keep up. This is why Quality Assurance today is deeply connected to DevOps and CI/CD pipelines. QA & Automation Engineers don’t just test software at the end. They embed testing into the delivery process itself. In a modern DevOps setup: - code is written - tests run automatically - builds are validated - deployments are approved or blocked - all without human intervention QA Engineers make this possible by: - writing automated tests that runs inside CI/CD pipelines - validating APIs before frontend users ever see changes - ensuring every deployment meets quality standards - working closely with DevOps to stop bad releases early They use tools such as: - Selenium/Playwright - automated UI testing - API testing tools - backend validation - CI/CD pipelines - continuous testing and delivery - Scripting (Python/JavaScript) - test logic and automation In short: DevOps moves software fast. QA ensures it moves safely. If you enjoy logic, analysis, systems thinking, and protecting users from failure, QA & Test Automation - especially within DevOps pipelines - may be your path.
Reuben Dickson tweet media
English
4
1
9
417
EnableEdge
EnableEdge@EnableEdge·
@alexinbinary Does it do any e2e/integration testing? only code review as QA engineer is incomplete
English
0
0
0
17
Alex
Alex@alexinbinary·
We built the first AI QA Engineer. We just deployed the best tool on the market when it comes to reducing slop and pushing quality. And it doesn’t even come close. Now in research-preview for growing startups.
English
82
41
382
61.2K
EnableEdge
EnableEdge@EnableEdge·
@Shubham_TheQA I liked the part where we are focusing on unit testing. Even if we can do unit testing well it will be really helpful for team to deliver good quality feature/functionality. I am not sure about doing e2e in-sprint and reason mostly will be time constraint
English
0
0
0
10
Helder Perez
Helder Perez@helderbuilds·
@EnableEdge Indian Test Data Generator is such a specific, needed fix. The regex for valid Indian phone numbers alone is a nightmare. Does it handle regional IDs or just the basics for now?
English
1
0
1
5
EnableEdge
EnableEdge@EnableEdge·
@Lockhead Exactly. AI in production raises the bar for testing and observability. Quality, reliability, and monitoring can’t be afterthoughts anymore.
English
1
0
0
18
Johannes Koch
Johannes Koch@Lockhead·
I'm eager to see how we all adapt using AI not only for PoCs but also for production-grade software and how we continue to ensure a high quality of delivery... And also now we observe our applications in the future... #BuildInPublic #SaaS #AWS #AWSCommunity #Observability
English
2
0
2
77
EnableEdge
EnableEdge@EnableEdge·
@Jsergioding Well said. Catching issues early is far cheaper than fixing them in production. QA is about protecting users, teams, and revenue.
English
1
0
1
20
Sergio | QA for Web & Apps
Sergio | QA for Web & Apps@Jsergioding·
Founders: Bugs cost more after launch. – refunds – bad reviews – emergency fixes – team burnout QA isn’t overhead. It’s insurance.
English
1
0
1
44
EnableEdge
EnableEdge@EnableEdge·
@championswimmer Exactly. QA shouldn’t be a safety net for unstable builds. Strong dev testing + clear acceptance criteria = faster approvals and better quality.
English
0
0
0
6
Arnav Gupta
Arnav Gupta@championswimmer·
If your org has a manual user-testing QA team - here's something as a developer you must understand. If you make a build, share with QA, and QA reports defects/regressions and sends it back for you to fix - this is not supposed to be the norm, but the exception. Norm should be 99% times QA team doesn't find any issue and approves it.
English
21
14
250
51K
EnableEdge
EnableEdge@EnableEdge·
@granttheeking Solid flow 👍 We’ve seen quality improve when testing starts at ideation & design, not just at QA/UAT. Shift-left saves rework later.
English
0
0
0
3
Grant ❂
Grant ❂@granttheeking·
For me, these are the necessary processes required in building a successful product: 1. Ideation 2. User Research & Discovery 3. BRD Creation 4. PRD Creation 5. Alignment with PM & Engineering 6. Product Design 7. Back-end Implementation 8. Front-end Implementation 9. Design QA & Iterations 10. Endpoint Integration 11. Testing (QA/UAT) 12. Deployment 13. Post-Launch Monitoring & Continuous Improvement
English
4
3
26
1.1K
Marshall
Marshall@mdnlabs·
Gm legends. Share what you're building this Tuesday. 🚀 Support someone's project! 🔥
English
253
1
180
8.7K
EnableEdge
EnableEdge@EnableEdge·
@techcoachralph Even before you start your work communicate with stake holders about what critical parts of application should be covered then highlight the risks in terms of 1. What features were tested 2. What were not 3. During our testing what critical issues were found
English
1
0
0
7
Tech Coach Ralph
Tech Coach Ralph@techcoachralph·
I often wonder: how do you handle the pressure of balancing quality with tight deadlines? As a QA Engineer, I've faced that struggle many times. Do you compromise on standards for speed, or push back—and risk being seen as an obstruction? Let's talk about it. #QA #SoftwareTesting
English
1
0
0
17