Closed shawnpyle closed 5 years ago
Hi Shawn,
I'm really sorry I'm not in a position to help you with this.
I last looked at this project 5 years ago and my knowledge of it all has left me.
When I was working on this I spent a lot of time in the adobe help boards, each adobe product had a pretty decent community of developers working on it. Hopefully you can find something there.
Good luck buddy.
/t
Thanks for the update!
For posterity, it was jasmine's asynchronous spec running that was causing problems. Disabling that functionality allowed me to run many tests. theasci/jasminejsx has been updated accordingly.
spyle@437 jasminejsx|master$ ./specRunner.sh
Starting ExtendScript specs...
Be sure you are signed into the Creative Cloud app or you'll get no output from the test suite.
1|2019-09-05T12:48:15|INFO|***************************
2|2019-09-05T12:48:15|INFO|Jasmine ExtendScript Runner
3|2019-09-05T12:48:15|INFO|***************************
4|2019-09-05T12:48:40|INFO|51 specs, 0 failures, 51 pending specs
5|2019-09-05T12:48:41|INFO|Finished in 0.221 seconds
Time to complete: 1.443 seconds
Hello @tmaslen, Thanks for your work on this project! It's been helpful getting up and running with ExtendScript.
I'm working on a new Adobe CEP module and I'd love to use this library to test my host JSX. However, I'm seeing something odd and was hoping you might be able to point me in the right direction, or at this point, any direction.
You can see my updates at https://github.com/shawnpyle/jasminejsx. Essentially, I've removed the need for the Toolkit by using Apple JavaScript for automation and using a custom
LogReporter
(slight modifications to yourJsxrReporter
. However, I'm seeing that if I have a number of specs (31, seespec/SpecLength.jsx
for more details) output fails to be logged.Results looks like this:
but I would expect it to look like this:
My questions are thus:
Thanks in advance for any help you can provide.