PDA

View Full Version : Sencha Test trial version of 1.0.3 not working



bhartiTidake
3 Aug 2016, 2:50 AM
Sencha Test trial version of 1.0.3 not working.Not showing test case pass or fail and not even the error just load browser on selection before we click on run.
just say loading test as below image

vojtech.cerveny
3 Aug 2016, 10:43 PM
Hi,
if you tried example from Docs, we have some difficulties with it - I hope that we will change it.

But 1.0.3 works ;)


Can you try this?


Create new workspace
Project Settings - Location (URL): https://translate.google.com
Save it
Add new js file to Scenario.
Add this code:
describe("GoogleTranslate", function() {
it("should write Sencha Test", function() {
ST.element('#source')
.type('SenchaTest')
.and(function(textarea){
expect(textarea.dom.value).toBe('SenchaTest');
});
});
});
Run your code :)

You should have same result as me:
54888

Feel free to contact me any time.
Vojt?ch

Abhijit Muke Interface
4 Aug 2016, 2:52 AM
Thanks vojtech,


We were also trying to use sencha test with our application, but due to that kind of documentation problem, we stuck in between.

Can you please refers some link, by which we can gain more knowledge about this tool to use it with our sencha application.

Also, please suggest,

1) From where we should start ?
2) Why Sencha test ?
3) how to generate test report ?

I have one doubt to ask you, are there any function which are disabled in trial version ?


Thanks

vojtech.cerveny
5 Aug 2016, 12:06 AM
Some links:

http://jasmine.github.io/2.4/introduction.html ST uses Jasmine framework - it is good to know how jasmine works
http://docs.sencha.com/sencha_test/index.html Documentation provides some examples, explains how SenchaTest works
https://www.sencha.com/blog/sencha-test-examples-part-1/ Don Griffin wrote very nice article on Sencha Blog - look at it. I like second part, very nice demostration of using SenchaTest

And my suggestion:
1. Try generate default app and try write some first test - clicking on grid, clicking on tabs, check if visibility of panels is changed etc. You can use event recorder, but I highly recommended to use ST API, which is more readable and better for writing.
2. Why ST? Tricky question :) This is my personal opinion - SenchaTest has very nice feature, that you can test your app on hundreds browsers in same time. You just add BrowserStack or SauceLabs and you are ready to test your app on big amount of browsers (with some settings obliviously). And you can automatize it with Sencha Test Command (console runner of SenchaTest) and grab your results to ArchiveServer or send it to Jenkins or what you want. Then senchaTest is able test unit test in your app, so you are able split your components and test it separately. I have some experience with some other testing programs and I have good feeling about Sencha Test - for me it is very good program for testing your ExtJS (or non-ExtJS) apps. And of course it has some bugs, but dev team works on it and Sencha Test is better and better in every release.
3. What you need is stc (Sencha Test Command) - look at Documentation (http://docs.sencha.com/sencha_test/guides/command_line_archive_server.html) for it. JUnit and Teamcity reports are supported.

Trial has same functions as Paid version, but it is limited by time - obliviously :)


If you have some other question, feel free to contact me any time.
Vojt?ch