Katalon with GitLab CI, katalon is not recognized as an internal or external command - ui-automation

I am trying to setup a simple TESTSUITE with katalon to run automatically on Gitlab but I keep hitting this error :
katalon is not recognized as an internal or external command when i run this script:
I have followed this tutorial. And tried using katalon-execute.sh instead of katalon but no changes
https://docs.katalon.com/katalon-studio/tutorials/continuous_integration_gitlab.html#add-katalon-path-to-environment-variables
Some help would be really appreciated.
run_katalon_test_suite:
tags:
- shell
script:
katalon -noSplash -runMode=console -consoleLog -projectPath=
"My project path>" -retry=0
-testSuitePath="Test Suites/FirstTestSuite>" -executionProfile=
"default" -browserType="Chrome (headless)"

You need to navigate to the folder where Katalon is installed and then run the console command from that folder.

If it is shell script then it should start with ./
The solution will need a change in the shell script.
./katalon -noSplash -runMode=console -consoleLog -projectPath=
"My project path>" -retry=0
-testSuitePath="Test Suites/FirstTestSuite>" -executionProfile=
"default" -browserType="Chrome (headless)"

Let's say if u katalon IDE is located in ur Desktop
"C:/Users/xxx/Desktop/Katalon_windows/Katalon.exe" -noSplash -runMode=console -consoleLog -projectPath="My project path>" -retry=0 -testSuitePath="Test Suites/FirstTestSuite>" -executionProfile= "default" -browserType="Chrome (headless)"

Related

VSCode Pytest - Python Test Explorer is able to find test but doesn't run them with correct path

My VSCode is able to find all my tests and lets my run them from the explorer, but upon running them it is calling the wrong path. I'm using a Poetry virtual environment which is in a different path than the tests.
From the Python Test Adapter Log:
INFO pytest at 'myproject': Running pytest with arguments: --rootdir=/Users/me/Desktop/myproject , Users/me/Desktop/project/tests/db/queries/my_test.py::test_fn
INFO pytest at 'myproject': Running /Users/me/Library/Caches/pypoetry/virtualenvs/myproject-api-NEejG4ix-py3.9/bin/pytest as an executable
CRIT pytest at 'myproject': Execution of the test Users/me/Desktop/project/tests/db/queries/my_test.py::test_fn" failed: Error: Process exited with code 4: ERROR: file or directory not found:
VSCode Settings:
"python.testing.pytestPath": "/Users/me/Library/Caches/pypoetry/virtualenvs/myproject-api-NEejG4ix-py3.9/bin/pytest",
"python.testing.unittestEnabled": false,
"python.testing.pytestEnabled": true,
"python.testing.pytestArgs": ["api/tests"],
Using this VSCode extension ID: littlefoxteam.vscode-python-test-adapter
Is there another setting for setting the path when running from the test explorer extension?

Eclipse (atollic) Pre-Build command format

I'm using Eclipe-Atollic to build for a STM32 micro. Running Windows 10 and TortoiseSvn. Im trying to get the Svn version into my code using the Tortoise "svnversion" command.
I'm trying to add the following command to the Pre-build steps in Eclipse-atollic under "Project Properties >> C/C++ Build >> Settings >> Build Steps >> Pre-build steps" .
svnversion > Src\svnvers.inc
This works fine from the Command prompt, but when I use the Eclipse builder - I get the following error message:
Info: Internal Builder is used for build
svnversion > Src\svnvers.inc
svnversion: E020024: Error resolving case of '>'
After the initial error, I've tried a variety of combinations of " and \ escapes, but without success.
Looking for any guidance on how to configure Eclipse to execute this command.
Thanks,
OK, If anyone else needs to know, I used "cmd -c" to execute the command, so what worked was:
cmd -c svnversion > Src\svnvers.inc

Codewarrior's command-line interface stops waiting for a dialog

I am compiling a CodeWarrior project using cwide.
When the build is successful, everything is OK, but when there are errors, my continuous automation system blocks forever waiting for a click here:
I invoke the build with:
cwidec -noSplash -data $WSWORKSPACE -application org.eclipse.cdt.managedbuilder.core.headlessbuild -build ProjectName
Any ideas, how to avoid that dialog?
The solution is adding --launcher.supressErrors.

How to release windows build of ionic app?

I am trying to release windows build of ionic app used below two command ionic platform add windows and ionic build windows but at the time of run second command getting following error at cmd
D:\#Ionic\ChefsRecipes>ionic build windows
Running command: "C:\Program Files\nodejs\node.exe" D:\#Ionic\ChefsRecipes\hooks\after_prepare\010_add_platform_class.js D:\#Ionic\ChefsRecipes
add to body class: platform-windows
Error: No valid MSBuild was detected for the selected target.
I have set PATH variable to "C:\Windows\Microsoft.NET\Framework64\v4.0.30319;". I am using windows 8.0 please suggest me right step for release build for windows ?

send an email using monkey talk automation tool

Is it possible to send an html email report through a monkey talk automation tool. If it is possible please provide any code or url.
Thanks,
Ramakrishna.
Use a CI (continuous Integration tool) with monkeytalk.
like jenkins+monkeytalk it is bit hard to configure it. but it can be done. use jenkins to automate the process of checkout code from repository and write a shell script to build the project and runtest cases with monkeytalk. after finish tests jenkins will email the reports to the given recipients.
jenkins: http://jenkins-ci.org/
More details...
first of all you need to download and deploy Jenkins. Downloadlink
to deploy in terminal
$ java -jar jenkins.war
open a browser http://localhost:8080 will take you to Jenkins dash board.
There is link for Jenkins settings on left side menu: from that page you can set an email account , password for Jenkins. and then provide recipient email addresses. so if a build faild Jenkins will email all console errors to the recipents. (try reading Jenkins documentation if it hard to install)
Then create a new job giving a name and details . add your repository URL and type add user credientials to it. and configure the rest in the end of the page you can give a build command as a shell script or ant file or there are many options.
then save the job and edit configurations start a build if it not checkout your code from repo and build correctly copy the errors from error console and search in google.
here is a sample code for build a Xcode project to a simulator
echo "Build Start"
/usr/bin/xcodebuild -target FuncTest CODE_SIGN_IDENTITY="iPhone Distribution: Leapset Inc." PROVISIONING_PROFILE="xxxxxxxx-1216-4E86-97D5-xxxxxxxxxxxx" OTHER_LDFLAGS="-lxml2 -all_load -lstdc++" DSTROOT="build" VALID_ARCHS="armv7 armv7s i386" -arch i386 -sdk iphonesimulator6.0 -configuration Release clean build install;
echo "Build End"
if you need to open iPhone simulator with the app use
# open app in simulator
echo "Start run app in simulator"
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Applications/iPhone\ Simulator.app/Contents/MacOS/iPhone\ Simulator -SimulateApplication release-1.081/Leapset/build/Release-iphonesimulator/LeapsetFuncTest.app/FuncTest & disown;
echo "DONE run app in simulator"
run tests
echo "start run Test jobs"
######### Job 1 #########
echo
echo "TEST: SignInOut.mts"
echo "DISCRIPTION: sign in and out with user credintials"
#java -jar $$ROOTPATH/monkeytalk/LeapsetTest/libs/monkeytalk-runner-1.0.43.jar -agent IOS $ROOTPATH/monkeytalk/LeapsetTest/signinUser.mt
java -jar monkeytalk/LeapsetTest/libs/monkeytalk-runner-1.0.43.jar -agent IOS monkeytalk/LeapsetTest/SignInOut.mts
and monkey talk will generate reports. only thing you need to find is some way to attach those html reports to the Jenkins There are so many plugging available for Jenkins.
above commodes are working fine but you need to give the corrects paths to work it. like for above build command
Note: this command should run in terminal inside the project root directory(where the Xcode project file is)
Good luck
:)
xocdebuild command help
xcodebuild
[-project <projectname>]
[[-target <targetname>]...|-alltargets]
[-configuration <configurationname>]
[-arch <architecture>]... [-sdk [<sdkname>|<sdkpath>]]
[-showBuildSettings] [<buildsetting>=<value>]... [<buildaction>]...
xcodebuild
[-project <projectname>] -scheme <schemeName>
[-configuration <configurationname>]
[-arch <architecture>]... [-sdk [<sdkname>|<sdkpath>]]
[-showBuildSettings] [<buildsetting>=<value>]... [<buildaction>]...
xcodebuild
-workspace <workspacename> -scheme <schemeName>
[-configuration <configurationname>]
[-arch <architecture>]... [-sdk [<sdkname>|<sdkpath>]]
[-showBuildSettings] [<buildsetting>=<value>]... [<buildaction>]...
xcodebuild -version [-sdk [<sdkfullpath>|<sdkname>] [<infoitem>] ]
xcodebuild -list [[-project <projectname>]|[-workspace <workspacename>]]
xcodebuild -showsdks