Bugs

Despite having several flaky tests the chart which shows them over time displays zero flaky tests.

We have several tests that are failing with multiple assertion errors, but in Qase they are marked as Invalid. We use expect.soft() to report every assertion error when evaluation the response body of our API tests using playwright. But for some reason, these tests are not being properly marked as Failed, but instead show as Invalid - which confuses the team and makes them think the test errored out instead of just failing due to bugs. This began happening when upgrading to 2.1.7 of the playwright-qase-reporter. Can someone please update the status evaluation logic to ensure it works for multiple failed expect.soft() playwright assertions? Update: this may not be limited to array of errors, but instead may affect GenericAssertions ( https://playwright.dev/docs/api/class-genericassertions ) that don't result in the expected error message. Attached is an example, where we have two expect.soft assertions asserting the value of some json data (results of an accessibility scan) match some criteria. The error uses a custom message in the expect() call rather than the standard messaging

I have test suite administration which contains sub-suites. Administration suite does not have any test cases within or just one (in screen attached) but embeded suites have. During adding test cases to test plan when I click on administration to show me list of all cases and sub-suites list of cases from main suite takes up most of the window while every other thing is pushed down which makes it less visible.

When viewing a test-case using the path app.qase.io/case/ ... if parameter values reach a certain length, they start to push key parts of test-case UI out of the viewport, and it's impossible to scroll to the left, as evident in the screenshot. This is happening in Chrome 143.0.7499.170

Something is up with your authentication. I cannot log in using my Google account. When I select the ‘Continue with Google’ option, I am brought right back to https://app.qase.io/login .

AIDEN frequently adds unnecessary preconditions like: "Incognito/private browser session with no login. DevTools console access is available." "Two separate browser profiles or devices. DevTools console access is available." " Browser A is a normal session; Browser B is an incognito/private session. DevTools console access is available." These points are either handled in test steps (e.g. In Browser A navigate to....) or are not necessary to be spelled-out and just serve as bloat ("DevTools console access is available")

Given I am in the Queries page When I create a New query to search Test run Then I cannot add environment as one of the attributes for the search whereas I can use any other attribute Expected result : environment should be available as an attribute in the query

When a user edits an existing test run, all saved fields are pre-filled except the “description” field. The description appears empty even though the user previously entered content

The inability to update the result status of a test case is a bug. This is not a feature request. The ability to update a test case's result status is a common feature in any test tool. The current workaround is to use the Run Again feature which creates an additional test run record.

We have encountered this twice in the past 2 weeks. We selected 1 test case to delete only, but it ended up deleted the whole suite(and more) instead without any prompt for confirmation. Over 2K test cases were deleted and we have to restore all of them 1 by 1 on the Trash Bin page.