Hi @NickColley!
first of all thanks for your contribution in a11y tooling, it definitely helps making apps more inclusive. Regarding my issue, some of my tests are timing out after having jest-aXe integrated in my React Testing Library suite. I do have a quite recent version of RTL so cleanup won't help.
It is interesting to point that tests would pass:
--runInBand flag was used
Regarding the context of tests, all of them are "wrapper" components (like forms) and not bare elements, and they don't really make any extra assertions. They are just rendered and then passed to jest-aXe. It should be noted that prior to aXe's integration, their it renders correctly case would never have any issues. AFAIK, at the time of the timeout <body /> is empty.
Have already tried fiddling with the testTimeout and --max-old-space-size to no avail.
Any ideas of what might be the culprit or steps to identify potential problems are more than welcome.
Thanks in advance!
Hi @NickColley!
first of all thanks for your contribution in a11y tooling, it definitely helps making apps more inclusive. Regarding my issue, some of my tests are timing out after having jest-aXe integrated in my React Testing Library suite. I do have a quite recent version of RTL so cleanup won't help.
It is interesting to point that tests would pass:
--runInBandflag was usedRegarding the context of tests, all of them are "wrapper" components (like forms) and not bare elements, and they don't really make any extra assertions. They are just rendered and then passed to jest-aXe. It should be noted that prior to aXe's integration, their
it renders correctlycase would never have any issues. AFAIK, at the time of the timeout<body />is empty.Have already tried fiddling with the
testTimeoutand--max-old-space-sizeto no avail.Any ideas of what might be the culprit or steps to identify potential problems are more than welcome.
Thanks in advance!