Hi,
Test Complete from SmartBear is what Actian use internally.
I understand that changes have been made in OpenROAD 6+ to ensure Test Complete can drive OpenROAD.
The trouble with Test Complete in my experience is that the sales people call you the second the product has downloaded and then call you every week for a number of months thereafter.
We will be trying Test Complete with one of our clients when we get them onto 6 later this year.
There are a number of presentations on this and other test techniques in the London Actian conference in October.
Cheers
Adrian
--
You received this message because you are subscribed to the Google Groups
"OpenROAD Users Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to openroad-user...@googlegroups.com.
To post to this group, send email to openroa...@googlegroups.com.
Visit this group at https://groups.google.com/group/openroad-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/openroad-users/CAHajRQ7dyTm9rsoBiq63%3DeR4Ok2VMpU0tVYFpsSH1tHAjR%2BcKw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Hi Charaka,
As Adrian mentioned we are using TestComplete for GUI tests, that is wherever visual representation with user interaction (mouse clicks, data entry )is required (User Frames, Installer, etc.).
Anyway a big part of our automated tests run without any user interaction.
These could be tests for new features (e.g. new classes, attributes, methods, etc.), but also regression tests for bugs we fixed.
For those tests we use automated unit testing.
Our unit tests are written in OpenROAD (4GL) using our OpenROAD Unit Testing Framework,
which is available from
https://github.com/ActianCorp/OpenROAD_UnitTestFramework
(downloadable ZIP archive https://github.com/ActianCorp/OpenROAD_UnitTestFramework/archive/master.zip).
The automation is mainly done using batch/shell scripts, which
· Get the latest scripts and unit tests (XML export files, and required resources) from a version control system (Git/Stash repository)
· Import the XML export files as applications into a test database
·
Run the tests using rundbapp, makeimage/runimage, or special runner script
(so we could build a shared library before testing an application using its 3GL procedures);
handle run timeouts (e.g. for "hang" situations)
· Print test results including performance stats
BTW: One of my presentations during the upcoming event on 11 October 2016 in London has the title "OpenROAD Daily Build and Test Automation".
Kind regards,
Bodo.
Bodo Bergmann
Principal Software Engineer
Actian | Engineering
GESELLSCHAFTSANGABEN: Geschäftsführer: Steven R. Springsteel, Stephen Mark Padgett, Markus Bockle
Sitz der Gesellschaft: Hamburg| Handelsregister: Amtsgericht Hamburg | HRB 135991| USt-IdNr: DE252449897
To view this discussion on the web visit https://groups.google.com/d/msgid/openroad-users/005701d1fd16%2434f64e40%249ee2eac0%24%40demon.co.uk.
Thank you Bodo, Adrian
Greatly appreciate your comments.
Kind Regards,
Charaka Wijerathne