FeedLog-User Feedback Collector: Oct 04, 2026

Weekend Testing FeedLog group picture

Weekend Testing FeedLog session

Participants

  • Vishnu Priya – Andinolabs, Chennai | Deliverable
  • Yogeshwari Dhanasekaran – Payoda Technology Inc, Chennai | Deliverable
  • Karthik Kumar T J – Cognizant, Chennai
  • Uma Baskaran – Software Testing Enthusiast, Chennai
  • Thameemul Sadiq – BNP Paribas, Chennai
  • Kaspar Mary – Zuci Systems, Chennai
  • Karthik N – Mako IT Lab, Chennai
  • Indhu B – Software Testing Enthusiast, Chennai
  • Ajay Balamurugadas & Ganesh Manoharan – Facilitators

Charter

Explore FeedLog’s core areas (Feedback, Roadmap, Changelog and Dashboard) using a fresh account, to model key features and produce a short testable feature list.
Timebox: 40 minutes, followed by a group discussion.

Date

October 04, 2026, 5.30 PM – 7 PM IST

Brief summary of interesting findings/views

The most interesting finding of the session came from two testers looking at the same feature from opposite ends. Vishnu Priya took a structured route, writing 16 test cases that followed a single item from Feedback to Roadmap to Changelog. Fourteen passed, but two exposed a real gap: a changelog could be published while its roadmap item was still in Planned or In Progress, with no block or warning — meaning customers could be told about an update that hasn’t actually shipped. Yogeshwari hit the same area from the other side: she couldn’t work out how to publish a completed ticket at all. Put together, the publish step seems to be both too easy to reach for unfinished work and too hard to discover for finished work.

Yogeshwari’s exploratory notes also picked up a range of smaller issues a new customer would likely run into in their first few minutes. Switching accounts silently logged out the previous one. Images added to feedback were stored as links that she couldn’t open later, and text in image comments overflowed the comment box. The Detail field gave no hint of its character limit, and changing the language only translated parts of the app. Two of her observations raise questions rather than clear bugs: a “Found Similar Post” message appeared every time she created a new request, which makes you wonder how strict the duplicate detection is (Vishnu Priya’s duplicate-feedback test passed), and a “0” on the Roadmap page had no label or context to explain what it was counting. Overall, the two approaches complemented each other nicely — the test-case route found a logic flaw in the workflow, while free exploration surfaced the usability rough edges.