-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Key error: 'testCaseId' #39
Comments
A test json should contain a testCaseId. What allure version / language are you using? |
Python |
Are you using the exe? If so instead try installing via pip. |
no, i just installed it via pip and tried using the command line |
Ran a few tests with newest allure-pytest 2.13.1 and everything went fine. You can try on these example test rsults. If you get the same error something in your system is broken. Else you have to provide more information about what tests you run. Possibly if you have some more advanced pytest/allure techniques. Not every features were tested and are safe to work. Edit: Checkout https://github.com/typhoon-hil/allure-docx/blob/master/.github/issue_template.md |
understood, in the case I use behave, will that be the difference? I will compare the results of allure and if I see something I will comment again, thanks for the help |
Have you solved the problem? I also meeting the same problem. |
I have tried 'example test results',it is ok.However,I meeting the same error 'Key error: 'testCaseId' ' for my test results. |
I couldn't solve it, I ended up leaving it aside |
Did you work with allure-behave also? I'm not experienced with behave so unfortunatly I cannot tell what leads to the error but if you use it too it is likely that this is the problem, as behave was not tested. |
I have the same issue, and problem is probably quite simple, testCaseId is optional attribute, my tests are not decorated with this attribute |
See #44 (comment) . I fixed the issue in my fork (see merge request) |
I don't know if I did something wrong in the installation, but this error simply appears when I try to make the call
"allure-docx allure_json report.docx"
The text was updated successfully, but these errors were encountered: