"description": "Bitbar Cloud Appium Server Side Test Example",Īs you can see I used chai (because I wanted to use the BDD approach) and junit-reporter (because Bitbar devs are Java freaks and you can guess from samples that Cloud is reading JUnit files to read test methods). you may not use this file except in compliance with the. png`) įs.writeFileSync(filePath, screenshot, 'base64') Licensed under the Apache License, Version 2.0 (the License). My main.js (I have used bitbar-sample-app.apk and test method first from the top) : describe('Bitbar Sample App', () =>. # Make sure there's no pre-existing `screenshots` file blocking symbolic link creation This is how my run-tests.sh looks like: #!/usr/bin/env bash I have used Webdriver.io Testrunner - This is why I have and test/specs/main.js.
Bitbar technologies zip#
Looking at Python and Ruby examples this is how my ZIP structure looks like.
And because this is a simple bash script, you are free what this script will do. So, in theory, you can have in ZIP package only run-tests.sh file. The most important is the run-tests.sh file, it is responsible for starting the test execution in the cloud and also installing requirements. Here we will go through the files and also the correct makeup of the test zip. This package must contain test files, data files and needs to have a Shell script to launch test execution at the root level of the package.įor the cloud side execution to work properly, it is important to have the test suite zip outfitted with the right files.
All needed files for testing need to be uploaded to cloud as zip package.
0 kommentar(er)
