Christian_N_DK
Contributor
Joined 11 years ago
User Profile
User Widgets
Contributions
Installing Testexecute on a fresh virtual machine with IB based license silently
Hi, I am looking into migrating to ID based licenses. We are having an environment with temporary virtual machines, som keeping the ability to install and hook up to license silent is key. Have anyone a solution doing this with ID based licensing? The installation part is easy and done. But the setting up of licensing, with only commandline. I have not been able to find anything on this. Thanks 🙂Re: Jenkins Jobgeneration with DSL for Testexecute
Thanks for the reply. Our production code, look a little different, but does not work with newest credentials changes. But the differences are minimal. We generate almost all of our tests. Saves us a lot of maintenance of jobs.471Views0likes0CommentsJenkins Jobgeneration with DSL for Testexecute
Hi, I am having issues with generating jobs on Jenkins with the latest plugin updates for the Testcomplete plugin where credentials are a part of the job configuration. When generating the hash value for userPassword changes. And this brings me to the question, if the generated Hash, does have a timeout for validity? Or the generated jobs can "last for ever" with the generated hash value? I am using Job DSL on Jenkins for generating the test jobs, via groovy code. configure { it / builders << 'com.smartbear.jenkins.plugins.testcomplete.TcTestBuilder' { suite(suiteName) launchType('lcRoutine') project(projectName) unit(unitName) routine(rName) test('') executorType('TE') executorVersion('14.0') actionOnWarnings('MAKE_UNSTABLE') actionOnErrors('MAKE_FAILED') useTimeout('false') timeout('') useTCService('false') userName() userPassword('{ASecretPassword}') credentialsId('') useActiveSession('true') generateMHT('true') publishJUnitReports('true') } }504Views0likes2CommentsRe: How to execute multiple test suites from jenkins?
I am generating test instances on Jenkins with JobDSL plugin. I have an instance of anytest for basically any parameter I see as valid for seperating them. Example. We generate a set of instances for any release (we have multible ones ongoing), platfom, associated hardware, and some data differentiation also, Br, Christian1.8KViews2likes0CommentsRe: Sharing existing items with multiple projects
We have a very simple solution, which works fine for our need. We have a external tool used for some of our tests. All interaction for this is kept in a project solely for this. Mapping are needed for the tool in all the referencing projects within the project suite. But this tool rarely changes, so it is manageble. Also we keep some windows system "utilities" for for the test in the same project. This code is with out using namemapping. So this part is easy. Units from this "shered" project are imported as exsisting units into the projects where we need them. This works fine, within this scope. Br, Christian2KViews0likes0CommentsRe: What are our options to have versioning on tests?
Depending on what you think of. We have everything in GIT for source control. For creating multible instances of a test we have seperated test conditions, test sequence and data from eachother. Creating more reusable test sequences and data. We control what we execute by creating a test definition, which keeps the conditions, test sequence and data for the execution. After that we apply some magic trick with a script and run our test instances. Scaling with this approach is very fast. And managing data is easier than managing many scripts. Br, Christian1.5KViews0likes0CommentsRe: Multiple Node Lock Licenses
We are using GIT from source control. It works like a charm. But more important is an agreement of how to structure and write your test and code. We have an agreed way of structuring namemappings, so they are uniform and easy to find. Also fuctions/Keywords and so on need to be within some degree of uniform naming and structure. The more people you are, them more this matters. I may also suggest build a framework within TC, and refering to this from the tests. Making maintainability less and readbility higher. Works really well for us. We are about 15 testers contributing to the automated tests in different way. So we need to know what is going on always, Br, Christian561Views2likes0CommentsRe: Taking a license from the pool
Thanks for the reply. I have no way of knowing wo will trigger a test, or how many machines they will trigger. So we have manifested a more strict process for test executions. Within the environment, we have a simple script and a db, managing the licenses. It works fine. Even with bulk test initiations and 80 machines hamering away. This script, is now mandatory for taking and releasing a licens. Br, Christian1.8KViews1like0CommentsRe: Taking a license from the pool
Thanks for the reply. We are tightening the process for usage outside of the test environment. Within the environment, we have a simple script and a db, managing the licenses. It works fine. Even with bulk test initiations and 80 machines hamering away. Br, Christian1.7KViews0likes0Comments