You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've discovered that if the spec you start from lacks a components property and then you compare with a spec that has components added, running the summary command will cause a crash. Adding an empty components property to the starting spec fixes the problem.
Interestingly enough HTML report generation seems to work correctly without the empty property.
Here's a zip file with some minimal reproduction specs: examples.zip
(Note: adding an empty components property to the new file will also cause the crash but I've added a mock schema to be more correct to the real use case that produced the error)
And here is the command and result of running against the attached files:
Hello again, still a big fan of these tools!
I've discovered that if the spec you start from lacks a components property and then you compare with a spec that has components added, running the summary command will cause a crash. Adding an empty components property to the starting spec fixes the problem.
Interestingly enough HTML report generation seems to work correctly without the empty property.
Here's a zip file with some minimal reproduction specs: examples.zip
(Note: adding an empty components property to the new file will also cause the crash but I've added a mock schema to be more correct to the real use case that produced the error)
And here is the command and result of running against the attached files:
The text was updated successfully, but these errors were encountered: