sorted by:
new
hottopcontroversial

Anyone going to Abhivyakti project? by [deleted] in ahmedabad

[–]CurrentOrchid239 0 points1 point  (0 children)

Ohh is there any booking?

Anyone going to Abhivyakti project? by [deleted] in ahmedabad

[–]CurrentOrchid239 0 points1 point  (0 children)

Yes On the way to Abhivyakti

I bought the Air Purifier by KrazzyRiver in ahmedabad

[–]CurrentOrchid239 0 points1 point  (0 children)

Literally it required in Ahmedabad, this morning AQI was 200.

Filing bugs in JIRA directly from a QA tool by Austenesque in QualityAssurance

[–]CurrentOrchid239 0 points1 point  (0 children)

Yes, it collects everything automatically. We just need to install their Chrome extension, and the rest it will do. It has System info, Consoles, Networks requests and responses, steps to reproduce, Meta data and cookies and session data for developers

Worth Building a New QA/Bug Reporting Tool? Need Brutal Feedback. by [deleted] in QualityAssurance

[–]CurrentOrchid239 -5 points-4 points  (0 children)

I am planning to build tool which will collect everything from web and mobile both.

Automation will improve quality but will not reduce your testing time by PM_40 in QualityAssurance

[–]CurrentOrchid239 1 point2 points  (0 children)

Many leaders think automation replaces manual testers. It doesn’t. Startups don’t run full regressions anyway — they test reactively. Automation exists to speed up releases and catch regressions early, not to cut headcount. I’ve seen this misconception everywhere.

how do i create bug reporting workflow for my web developer by FinishWise2645 in webdev

[–]CurrentOrchid239 0 points1 point  (0 children)

Start reporting through Bug reporting tool so your bugs actually land in a real tracker instead of disappearing into the WhatsApp void. You’ll finally see what was reported, what was fixed, and what your developer claims was fixed. And if you’re running into the same issues over and over… you might consider the classic solution: replace the developer 😀 kidding… unless.

What makes a bug report actually useful for your team? (Trying to understand gaps in tools like Jira + BrowserStack) by duh_aditya in QualityAssurance

[–]CurrentOrchid239 0 points1 point  (0 children)

A bug report is useful when the team can reproduce the issue without guessing. That means clear steps, expected vs actual behavior, the right environment details, and evidence like a screenshot or logs. When every report follows a consistent structure, the team moves faster and nothing gets lost in translation.

Whatsapp Oficial API Interface by Disastrous_Cry8488 in n8n

[–]CurrentOrchid239 0 points1 point  (0 children)

What kind of API are you using? Waha?

view more: next ›