Automated testing

[rleir]

Hi all,

It has been a year since people talked here about automated testing so let's talk again. Do you have preferences between  Sikuli vs Selenium vs Watir vs Cucumber? For automated test runners, do you prefer  Jenkins vs Travis vs Circle-ci?

PTC/Thingworx folks please chip in, what do you use internally?

thanks -- Rick

[Kaya]

Hi Rick,

One recommendation we have is to use JUnit and integration tests (TestNg) for automated tests. It's also possible that there is a flavor of Selenium/cucumber tests for automating testing of UI. It could also be recommended to have all automated tests have jobs on your Jenkins build pipeline that get executed before approving the builds for release.

I also wrote a post on DevOps in ThingWorx that you can check out here.

-Kaya

[VladimirRosu · Accepted solution]

Especially for cases like this, one of my colleagues, created an example CI chain based on Jenkins, complete with a testing framework based on ThingWorx. Ideally he wants to upgrade it to do CD with Solution Central, but it all depends on our internal workload. That is, the expectation is on the community to enhance.

The chain is available here: https://bitbucket.org/CBadici/thingworxjenkinspipeline/src/master/

Disclaimer: this is not a PTC supported CI chain, so you should not open Tech Support cases for it. It's an example that is ideal for an experienced DevOps team and less for beginners in the art of Git.

[VladimirRosu]

Forgot to say that it does not contain UI tests, only functional/unit. But adding a Selenium test to Jenkins should not be rocketship work.

[rleir]

Vladimir

Very nice, thanks! 

cheers -- Rick