Have something to say?

Tell us how we could make the product more useful to you.

Provisional Pass

I have some tests which are simple Assert tests- my thought is…if the page loads and seems to have structural elements in place, it’s good. My tester selected an unstable image from a Related Posts page footer. For time pressure, I had to try to explain to my client that 12/18 was actually good. The page loads perfectly, the screenshot is beautiful, and it’s really a success by all indications. My suggestion is some rules for “Provisional Passage”, a status between Pass and Fail, where BugBug intelligently assists me. Maybe : Response code is 200 Response length is at least X, maybe 1K Response does not include phrases like “Error” Response includes at least one image or one YouTube link, which is valid.

Ken Lyle 11 days ago

Review process for tests

In the case of developers, there’s a review process from their colleagues before the fix/implementation is deployed on a specific environment. Similar to them, my team of QA are using Qase as a tool to organize our test cases repository, and that tool has a review feature where a test case is created, and the person marks it for review so at least 1-2 other QA people can offer feedback. As a QA lead that already does reviews for my QA colleagues on the test cases and test plans they create, I would find it very useful to have a similar feature in Bugbug for automated tests. Here’s an example of how the flow could work: The author creates a new Bugbug test that is marked in progress (using a dedicated label maybe? or a board?) Author finishes their work and mark it as “ready for review” Optional: a project setting could allow the administrator to set the number of review approvals before the automated test is ready to be added to a testsuite The reviewer opens the automated test in a dedicated view wherethey can see all the steps similary to today, except also have an intuitive interface where they can ask for changes and offer suggestions/feedback: suggest a new selector for a step, changing waiting conditions, using a different variable, create a new group inside the test, insert components, remove steps, remove groups etc (basically all the things that can be done at the moment during a test creation) Once the review suggestions are tackled by the author, they can send the test back to “In review” or they mark the test as “Done” (I don’t have full knowledge of best practices for review process that developers do), and it appears as usually in the test repository ready to be added to a testsuite I think the views of a test “in progress/review” would differ depending on who is the “Author” and who is the “Reviewer”. As a reference here is the documentation of Qase tool and their review process: https://docs.qase.io/general/get-started-with-the-qase-platform/test-cases/test-case-review

Marius COJOCARIU 27 days ago

1

An easier way to validate and work with table data

Use cases: In a data table for example, elements of the same type can be shown. It would be handy to be able to count the number of elements of the same type. Example 1: I added a record and I want to work on the last record/field. I don’t see a way to count the elements and then choose this number to find the last one. Example 2: I want to check the number of elements shown to check if this is the same number as what's expected. Example 3: I edited a field on the third row, after refreshing the page, I want to check if the same field in the third row was edited and has the correct value. I can find the field by value but I can’t check if it’s on the third row. Example 4: I use drag and drop to order rows, I want to check if the 6th row is correct.

Paweł Bylina 28 days ago

Add one or more tests to a testsuite directly from the Repository list

At the moment, managing a testsuite is a bit of a pain due to the way the search function works inside the testsuite modal, in the sense that when searching for a specific test, the results are not “filtered”, instead if there is a matching the test is highlighted with a border. Our repository has over 350 test cases and it’s a pain to have to scroll down the list of tests in order to visually pinpoint the highlighted matched test(s). An alternative to the above for me would be the ability to add one or more selected test(s) to one or multiple testsuite(s) directly from the repository, something like this: After clicking that, a modal would appear with a list of testsuite(s), and I could select one or more testsuites from there as a destination.

Marius COJOCARIU About 1 month ago

2

More User Roles (View Only, Run Only, Editor)

Hi BugBug Team, I'm a QA currently using BugBug for automating our test cases. We love how intuitive and fast your tool is! However, we’d like to request additional user roles or permission levels to better fit our organisational needs. Specifically, we’d like to see roles such as: View Only – can view test cases and run history, but cannot run or edit tests Run Only – can execute tests, but cannot edit or create them Editor – can create and edit tests, but cannot execute them unless permitted In our current setup, we don’t want developers to run tests, but we do want them to view run history and test artefacts for visibility. Right now, the permissions are a bit too broad for that.

Geetha Sriram About 2 months ago