- smoke test and demo the automagic power of xyteam/autobdd test framework;
- serve as a template for setting up a new autobdd test project.
- docker,
- docker-compose
- git
- vnc client/viewer
- mkdir -p $HOME/Projects
- git clone https://github.com/xyteam/autobdd-test.git $HOME/Projects/autobdd-test
docker-compose run --rm autobdd-test-run "make e2e-autorunner"
use browser to open searchable cucumber report
test-results/build-test/index.html
or
lauch a http server:
cd test-results
python -m http.server
then open a browser to http://host-ip:8000 to review the report
docker-compose run --rm autobdd-test-run "make k6-test"
docker-compose run --rm autobdd-test-run "make js-test"
docker-compose run --rm autobdd-test-run "make cy-test"
docker-compose run --rm autobdd-test-run "make py3-test"
docker-compose run --rm autobdd-test-run "make py2-test"
docker-compose run --rm autobdd-test-run "xvfb-runner.sh make test-all"
docker-compose up -d autobdd-test-dev
ssh -o StrictHostKeyChecking=no localhost -p 2224
or
ssh -o StrictHostKeyChecking=no [email protected] -p 2224
default password is *ubuntu*
vnc://ip.add.re.ss:5904
cd e2e-test/test-something
arunner.sh features/test_image.feature
arunner.sh features/test_ocr.feature:7
Observe browser GUI from vnc viewer
-
install vscode
-
in vscode install
2.1 remote development extension
2.2 gherkin/cucumber full support
-
in vscode open ssh target on port 2224
-
open folder $HOME/Projects/AutoBDD
-
go to test-projects to find your test project
-
start developing and testing
6.1 test code saved inside autobdd-test or BDD_PROJECT will persist inside and outside of the container
6.2 other code will not.
-
stop autobdd-test docker containers
1.1 docker-compose down
1.2 docker container prune -f
-
reset git
2.1 rm -rf autobdd-test/.git
2.2 git init
-
rename autobdd-test to new-project-name
3.1 edit .env, change BDD_PROJECT=autobdd-test to BDD_PROJECT=new-project-name
3.2 edit docker-compose.yml, update service name autobdd-test-run and autobdd-test-dev to new-project-name-run and new-project-name-dev respectively
3.3 optionally, to support multiple test projects, update port set 2224, 5904 and 8004 to 2226, 5906 and 8006 or 2228, 5908 and 8008, etc
-
test new project
4.1 docker-compose run --rm new-project-name-run "make xvfb-ruinner.sh test-all"
4.2 docker-compose up -d new-project-name-dev