Skip to content
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

Open
hellyson-herik opened this issue Apr 18, 2023 · 12 comments
Open

Key error: 'testCaseId' #39

hellyson-herik opened this issue Apr 18, 2023 · 12 comments

Comments

@hellyson-herik
Copy link

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"

@bjarnesc
Copy link

A test json should contain a testCaseId. What allure version / language are you using?

@hellyson-herik
Copy link
Author

Python
Allure 2.20.1

@bjarnesc
Copy link

Are you using the exe? If so instead try installing via pip.

@hellyson-herik
Copy link
Author

no, i just installed it via pip and tried using the command line

@bjarnesc
Copy link

bjarnesc commented Apr 19, 2023

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
Hard to help if so little information is provided.

@hellyson-herik
Copy link
Author

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

@feixu88
Copy link

feixu88 commented Jun 4, 2023

Have you solved the problem? I also meeting the same problem.

@feixu88
Copy link

feixu88 commented Jun 4, 2023

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 Hard to help if so little information is provided.

I have tried 'example test results',it is ok.However,I meeting the same error 'Key error: 'testCaseId' ' for my test results.

@hellyson-herik
Copy link
Author

Have you solved the problem? I also meeting the same problem.

I couldn't solve it, I ended up leaving it aside

@bjarnesc
Copy link

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 Hard to help if so little information is provided.

I have tried 'example test results',it is ok.However,I meeting the same error 'Key error: 'testCaseId' ' for my test results.

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.

@ggros
Copy link

ggros commented Nov 7, 2023

I have the same issue, and problem is probably quite simple, testCaseId is optional attribute, my tests are not decorated with this attribute

https://allurereport.org/docs/gettingstarted-readability/

https://allurereport.org/docs/junit5-reference/#id

@bjarnesc
Copy link

bjarnesc commented Nov 7, 2023

I have the same issue, and problem is probably quite simple, testCaseId is optional attribute, my tests are not decorated with this attribute

https://allurereport.org/docs/gettingstarted-readability/

https://allurereport.org/docs/junit5-reference/#id

See #44 (comment) . I fixed the issue in my fork (see merge request)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants