run cucumber selenium tests in gitlab-ci
Hi I have a selenium cucumber project with some tests. The tests worked and the chromeDriver had launch when I run the -mvn clean compile test in my IDE. I created this .gitlab-ci.yml in my project's root: image: markhobson/maven-chrome:jdk-11 stages: - build - test variables: MAVEN_OPTS: "-Dmaven.repo.local=.m2/repository" cache: paths: - .m2/repository/ - target/ build: stage: build script: - mvn $MAVEN_OPTS clean package - mvn compile test: stage: test script: - mvn test When I run the pipeline, I face this error in the console: Unable to load browser: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure. Build info: version: '4.0.0-beta-1', revision: '9c03156c2b' System info: host: 'runner-fa6cab46-project-25183469-concurrent-0', ip: '172.17.0.4', os.name: 'Linux', os.arch: 'amd64', os.version: '4.19.78-coreos', java.version: '11.0.10' Driver info: org.openqa.selenium.chrome.ChromeDriver What can I do for running the tests?8.8KViews0likes16CommentsSync Project with GitHub
I try to sync my feature files from GitHub to Cucumber Studio as described here: https://support.smartbear.com/cucumberstudio/docs/bdd-with-cucumber/index.html However, the screenshots look completely different from what I see. I cannot choose between different types of projects when I create a new one for example. Also there is no button 'Connect to your features'. I can only create new ones. This is what it looks like for me: Any idea what I do wrong?1.3KViews0likes0CommentsGitlab Improvements in 13.5
Does anyone know how the merge request pipelines for GitLab improvement specified in the release notes differs from the way that GitLab currently integrated into Collaborator? We currently use GitLab MRs to spawn reviews with the webhooks. https://support.smartbear.com/collaborator/docs/general-info/version-history/ver-13/ver-13-0.html#v13500506Views0likes1CommentAquiring Floating License from within docker container in gitlab-ci pipeline
Hi, I am starting theready-api-soapui-testrunner (https://hub.docker.com/r/smartbear/ready-api-soapui-testrunner) from within a git pipeline. The container starts and connects to the license server, but the license server asks which license type i want to aquire. At this point I am running in a git runner and there is no way to provide input to the container. Is there any way to provide this in the docker run command or something alike? Heres where the pipeline times out waiting for input: running image $ docker run -v="testproject":/project -v="testprojectr":/reports -e LICENSE_SERVER="xx.xx.xx.xx:9999" -i smartbear/ready-api-soapui-testrunner:latest Please select the tool for which you want to get the floating license: 1. SoapUI Pro 2. LoadUI Pro 3. Secure (if you have an old license) 4. ServiceV Pro 5. VirtServer 6. ReadyAPI Bundle 7. TestEngine 8. swaggerhub 9. swaggerhub2 Obviously at this point i cannot provide console input. Kind regardsSolved1.5KViews0likes5CommentsData source error using gitlab
Hello, While writing my tests, I import from csv.file data that are used in request (body) but when launched through GitLab, in allure reports my tests failed with : Error:java.io.FileNotFoundException: /projectDir/file.csv (No such file or directory) ----------------- Messages ------------------------------ Could you help me find the right way to write the path? The csv files are in /projectDir/TestSuite/file.csv I tried with ${projectDir}/TestSuiteName ${workspaceDir}/TestSuiteName /branch/projectName/TestSuiteNameSolved1.3KViews0likes4CommentsGitlab CI/CD license issue
Hi, I am running my project in Gitlab. But the error comes ofr license not found and please enter the absolute path. Also, in the smart bear community, its mentioned that if you get an error using maven, specify the absolute path but where we have to specify, is not mentioned. Please find this link: https://support.smartbear.com/readyapi/docs/integrations/maven/troubleshooting.html#license Can someone advise on this?Solved2.2KViews0likes2CommentsGitHub/GitLab Integration: Selectable default template by project
When a Collaborator review is created from a pull/merge request through the GitHub/GitLab remote integration, it would be nice if a template could be configured to be automatically selected based on the project the pull/merge request came from. Different projects may have different workflows, so setting a default template for the Collaborator review based on the project would set the proper workflow. Currently the default template is the last one the user creating the review (which is matched from the user creating the pull/merge request) used.938Views0likes0Comments