What problems is BrowserStack solving and how is that benefiting you?
Earlier, our team used Google Sheets for manual test case execution, which came with a few drawbacks: we couldn’t easily track execution history, we had limited visibility into overall progress, and assigning different cases to different team members was not very smooth. Now, with the BrowserStack test management tool, we have configurations that make it feasible to assign different cases to different people, and we can also see the edit history of test case execution.
Another major improvement is around bug reporting. With Google Sheets-based execution, we had to raise bugs directly in Jira and then later map them back to the relevant cases again. With BrowserStack, Jira issues can be raised from the same tool, which saves significant time.
That said, I do have a few pieces of feedback from a QA perspective that I feel should be improved, since they are frequent, time-consuming areas and currently feel like gaps in an end-to-end QA execution journey. Review collected by and hosted on G2.com.