-
If I use --qase-testops-plan-id=5 in CLI, I see qaseio.exceptions.ApiTypeError: Invalid type for variable 'id'. Required value type is int and passed type was str at ['id']
-
The problem is that Cypress creates a separate reporter for each test file. As a result, after running all the tests in each single file, the run test is marked as completed. Instead, it should be com…
gibiw updated
1 month ago
-
There is no standardized way to pass test parameters from an automated Jest test to the test result, to correctly discern the difference between the varying test cases
-
### Description
Users can create a new account in TMS Qase.io.
### Steps to reproduce
* *Step 1*
Action: Open "Sign Up" page: [https://qase.io/signup](https://qase.io/signup)
Expected Resul…
-
Besides attaching custom text snippets as attachments with `qase.attach()` users can find it useful to attach some comments that will be shown right on the results page.
# Value
Such syntax can …
-
I'd like to be able to set the Automation Status of test cases when using `qase.results.createResultBulk()`. The `ResultCreateCase` typescript type doesn't expose as many fields as the individual test…
-
I recently updated to v2.0.4 and it says that the old syntax is supported but when i run my tests I get this error
```
qase: qase(caseId) is deprecated. Use qase.id() and qase.title() inside the te…
-
I have encountered this error upon executiong my Junit cucumber runner file:
java.lang.NullPointerException: Cannot invoke "java.net.URL.toURI()" because the return value of "java.lang.ClassLoader.ge…
-
The following error happens when running tests with Qase reporters enabled in Playwright, Cypress, and other frameworks:
```
[ERROR] qase: Unable to publish the run results to the upstream reporte…
-
**Describe the bug**
Enabling qase on our build.yml file and running on MS playwright service is throwing an error.
**To Reproduce**
Steps to reproduce the behavior:
1. Step 1 'Running a test s…