This is a repost of a discussion I started.
I'm using chutzpah test adapter for the test explorer 3.0.1. When I start VS and go to the Test Explorer, I can see the output in the "Tests" console. It shows ------ Discover test started ------ and then has a timeout for every one of my test files: "Error: Timeout occured when executing test file".
I do have the chutzpah logging enabled, and it spits out lots of good stuff, but every discovered test file ends with phantom complaining that it timed out.
I was considering upgrading to 3.2.1, but when I installed it locally, I started getting failures when running tests from chutzpah context menu or console. The tests themselves succeeded, but they started failing because of functionality in a document.ready function...which previously didn't seem to be executed during test execution. I believe the two problems are related. I was not worried about the js tests not showing up in test explorer because they were still executable from the context menu or console. But if 3.2.1 is going to start failing because the execution of the document.ready function, then I realize I need a better picture into what's really going on.
The sample I'm attaching does not have any references to a document.ready function, so I think that I may be off on that thought...but it is still a problem with 3.2.1 where the execution of the document.ready function causes errors. It seems that in previous versions (at least in 3.0.1), the document.ready was not being run).
I included the chutzpah.log that was generated by the test discovery process.
Any help you can provide is much appreciated.
Comments: Working on the fix and plan to do a new release in a couple weeks at the latest.
I'm using chutzpah test adapter for the test explorer 3.0.1. When I start VS and go to the Test Explorer, I can see the output in the "Tests" console. It shows ------ Discover test started ------ and then has a timeout for every one of my test files: "Error: Timeout occured when executing test file".
I do have the chutzpah logging enabled, and it spits out lots of good stuff, but every discovered test file ends with phantom complaining that it timed out.
I was considering upgrading to 3.2.1, but when I installed it locally, I started getting failures when running tests from chutzpah context menu or console. The tests themselves succeeded, but they started failing because of functionality in a document.ready function...which previously didn't seem to be executed during test execution. I believe the two problems are related. I was not worried about the js tests not showing up in test explorer because they were still executable from the context menu or console. But if 3.2.1 is going to start failing because the execution of the document.ready function, then I realize I need a better picture into what's really going on.
The sample I'm attaching does not have any references to a document.ready function, so I think that I may be off on that thought...but it is still a problem with 3.2.1 where the execution of the document.ready function causes errors. It seems that in previous versions (at least in 3.0.1), the document.ready was not being run).
I included the chutzpah.log that was generated by the test discovery process.
Any help you can provide is much appreciated.
Comments: Working on the fix and plan to do a new release in a couple weeks at the latest.