A set of Gherkin Features and custom vardoc Context with custom step definitions, and assets, that helps with automated testing for vardoc project websites.
This page list all the steps needed, which you need to run the Behat Gherkin Features to test a vardoc website in your localhost machine.
To test vardoc 4.0.x in the right way you will need to build vardoc using the composer.
Create a vardoc project with Composer:
composer create-project vardot/vardoc:4.0.x-dev PROJECT_DIR_NAME --stability dev --no-interaction
cd path to your files of the project/PROJECT_DIR_NAME
composer require --dev drupal/core-dev:~9.0
composer require --dev drush/drush:~11.0
composer require --dev drupal/drupal-extension:~4.0 --with-all-dependencies
composer require --dev emuse/behat-html-formatter:^0.2.0
cd path to yout files of the project/PROJECT_DIR_NAME
BEHAT-SCREENSHOT to capture images on demand or when a test fails
composer require --dev drevops/behat-screenshot
Edit the behat.yml file, which is located in:
`path to your files of the project/PROJECT_DIR_NAME/docroot/profiles/vardoc/behat.yml`
- to have DrevOps\BehatScreenshotExtension\Context\ScreenshotContext under contexts
- to have DrevOps\BehatScreenshotExtension:
dir: '%paths.base%/tests/screenshots'
fail: true
fail_prefix: 'failed_'
purge: false
under extensions
Read more about it here: https://github.com/drevops/behat-screenshot
Have vardoc installed from the browser or using the drush site:install command.
But make sure to have the webmaster user with the dD.123123ddd passwrod.
Exmaple Drush install:
Change directory in the terminal to the path of the project and /PROJECT_DIR_NAME/docroot
../bin/drush site-install site-install vardoc --yes --account-name="webmaster" --account-pass="dD.123123ddd" --account-mail="webmaster@vardot.com" --db-url="mysql://root:rootpw@127.0.0.1/test_vardoc" --locale="en"
Needed to uninstall as the Antibot module will prevent the Selenium robot from performing effectively
cd `/PROJECT_DIR_NAME/docroot`
../bin/drush pm:uninstall antibot --yes
../bin/drush cr
cd `/PROJECT_DIR_NAME/docroot`
../bin/drush config:set system.performance css.preprocess 0 --yes
../bin/drush config:set system.performance js.preprocess 0 --yes
../bin/drush config:set system.logging error_level all --yes
../bin/drush cr
Change directory in the terminal to the path of the project
and /PROJECT_DIR_NAME/docroot/profiles/vardoc/scripts
And run the following base command
bash add-testing-users.sh
To delete testing users use
bash delete-testing-users.sh
Edit the behat.yml file, which is located in:
path to your files of the project/PROJECT_DIR_NAME/docroot/profiles/vardoc/behat.yml
to the domain or the local virtual domain.
base_url: 'http://localhost/testing/docroot'
change the worker selenium robot server and the port number by changing the parameter.
"wd_host: 127.0.0.1:4445/wd/hub"
in the behat.yml file.
Follow with the following steps to get all needed tools for selenium to work.
sudo apt update
sudo apt install -y openjdk-11-jre openjdk-11-jre-headless openjdk-11-jdk openjdk-11-jdk-headless
sudo apt-get install libappindicator1 fonts-liberation libgbm1 libgtk-3-0 xdg-utils
export CHROME_BIN=/usr/bin/google-chrome
wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
sudo dpkg -i google-chrome-stable_current_amd64.deb
rm google-chrome-stable_current_amd64.deb
CHROME_DRIVER_VERSION=$(wget -qO- chromedriver.storage.googleapis.com/LATEST_RELEASE);
echo $CHROME_DRIVER_VERSION;
wget http://chromedriver.storage.googleapis.com/$CHROME_DRIVER_VERSION/chromedriver_linux64.zip
unzip chromedriver_linux64.zip
sudo chmod +x chromedriver
sudo mv -f chromedriver /usr/bin/
rm chromedriver_linux64.zip
wget https://github.com/SeleniumHQ/selenium/releases/download/selenium-3.141.59/selenium-server-standalone-3.141.59.jar
$ java -jar selenium-*.jar -port 4445
To run the automated testing with behat you will need to change the [ wd_host and base_url ] settings in the [ behat.yml ] file to go with your project configuration and the selenium server.
Drupal\MinkExtension:
ajax_timeout: 60
files_path: "%paths.base%/tests/assets/"
goutte: ~
selenium2:
wd_host: 127.0.0.1:4445/wd/hub
capabilities:
# browser: 'firefox'
browser: 'chrome'
# browser: 'phantomjs'
nativeEvents: true
marionette: true
browserName: chrome
version: "*"
extra_capabilities:
loggingPrefs:
performance: ALL
browser: ALL
chromeOptions:
w3c: false
args:
- "--headless"
- "--start-maximized"
- "--disable-gpu"
- "--window-size=1600,1200"
- "--no-sandbox"
- "--disable-dev-shm-usage"
- "--disable-setuid-sandbox"
- "--disable-web-security"
- "--DNS-prefetch-disable"
- "--disable-translate"
- "--ignore-certificate-errors"
- "--test-type"
- "--disable-extensions"
- "--incognito"
- "--disable-infobars"
- "--remote-debugging-port=9222"
- "--allowed-ips=*"
- "--whitelisted-ips=*"
base_url: 'http://vardoc.test'
# browser_name: 'firefox'
browser_name: 'chrome'
# browser_name: 'phantomjs'
javascript_session: selenium2
Then go to [ PROJECT_DIR_NAME/docroot/profiles/vardoc ] in the terminal then you could run the following command:
$ ../../../bin/behat tests/features/vardoc
$ ../../../bin/behat tests/features/vardoc/01-website-base-requirements/01-01-user-registration_only-admins-login.feature
Feature: Website Base Requirements - User Registration - Only admins login
As an anonymous user
I will not be able to register as a user in the website
So that I will need a site admin or super admin to add me to the website
Background:
Given I am an anonymous user
@local @development @staging @production
Scenario: Check that create new account options does not appear for anonymous users.
When I go to "/user"
And I wait
Then I should not see "Create new account"
@local @development @staging @production
Scenario: Check that only admin can create an account.
When I go to "/user/register"
And I wait
Then I should see "Access denied"
@local @development @staging @production
Scenario: Verify that anonymous users cannot access admin pages.
When I go to "/admin"
And I wait
Then I should see "Access denied"
3 scenarios (3 passed)
9 steps (9 passed)
0m2.21s (59.89Mb)
$ ../../../bin/behat tests/features/vardoc/your-gherkin-feature.feature $ ../../../bin/behat tests/features/project-name/your-gherkin-feature.feature
$ ../../../bin/behat -di
- use -dl to just list definition expressions.
- use -di to show definitions with extended info.
- use -d 'needle' to find specific definitions.
All Varbase custom step definitions are tagged with #varbase tag.
Example: after a run for bin/behat -di command.
default | Then /^I should see image with the "([^"]*)" title text$/
| #varbase : To Find an image with the title text attribute.
| Example 1: Then I should see image with the "Flag Earth" title text
| at `VarbaseContext::iShouldSeeImageWithTheTitleText()`
default | Then /^I should see image with the "([^"]*)" alt text$/
| #varbase : To Find an image with the alt text attribute.
| Example 1: Then I should see image with the "Flag Earth" alt text
| at `VarbaseContext::iShouldSeeImageWithTheAltText()`
Scenarios are tagged with the Behat tags of:
- @local = Local
- @development = Development server.
- @staging = Staging and testing server.
- @production = Production live server.
So that we only run bin/behat --tags with the right tag for the environment.
Example:
$ ../../../bin/behat --tags '@development' tests/features/vardoc/
Which it will run Scenarios which has got the @development tag.
$ ../../../bin/behat --tags '@staging' ftests/eatures/vardoc/
Which it will run Scenarios which has got the @staging tag.
$ ../../../bin/behat --tags '@production' tests/features/vardoc/
Which it will run Scenarios which has got the @production tag.
PROJECT_DIR_NAME/docroot/profiles/vardoc/tests/reports/index.html
You will see the latest report for latest run.
if you want to custom a report you can add
--format pretty --out std
--format html --out reports/report-$( date '+%Y-%m-%d_%H-%M-%S' )
to format and select your output.
Example:
$ ../../../bin/behat tests/features/example.feature --format pretty --out std --format html --out reports/report-$( date '+%Y-%m-%d_%H-%M-%S' )
You will need to create the list of Testing users, and Add Arabic languages to the site.
You can run the following command:
$ ../../../bin/behat tests/features/vardoc/ --format pretty --out std --format html --out reports/report-$( date '+%Y-%m-%d_%H-%M-%S' )
After that you can see the report in the PROJECT_DIR_NAME/docroot/profiles/vardoc/tests/reports folder.
If you want to run the test in steps, if you are not interested in the initialization and cleaning up after the test.
$ ../../../bin/behat tests/features/vardoc
- @local = Local
- @development = Development server.
- @staging = Staging and testing server.
- @production = Production live server.
So that we only run bin/behat --tags with the right tag for the environment.
Run the vardoc check tests. Only to check, without any changes to the website.
cd docroot/profiles/vardoc;
../../../bin/behat tests/features/vardoc --tags '@check' --format pretty --out std --format html --out tests/reports/vardoc-check-tests-report-$( date '+%Y-%m-%d_%H-%M-%S' );
Run the vardoc full local tests. which developers could test all scenarios in their local machine environment.
cd docroot/profiles/vardoc;
../../../bin/behat tests/features/vardoc --tags '@local' --format pretty --out std --format html --out tests/reports/vardoc-full-local-tests-report-$( date '+%Y-%m-%d_%H-%M-%S' );
Run the vardoc full development tests. which developers could test scenarios on the website at the development environment.
cd docroot/profiles/vardoc;
../../../bin/behat tests/features/vardoc --tags '@development' --format pretty --out std --format html --out tests/reports/vardoc-full-development-tests-report-$( date '+%Y-%m-%d_%H-%M-%S' );
Run the vardoc full staging tests. which developers could test scenarios on the website at the staging environment.
cd docroot/profiles/vardoc;
../../../bin/behat tests/features/vardoc --tags '@staging' --format pretty --out std --format html --out tests/reports/vardoc-full-staging-tests-report-$( date '+%Y-%m-%d_%H-%M-%S' );
Run the vardoc full production only tests. not to change anything with test scenarios on the production environment.
cd docroot/profiles/vardoc;
../../../bin/behat tests/features/vardoc --tags '@production' --format pretty --out std --format html --out tests/reports/vardoc-full-production-tests-report-$( date '+%Y-%m-%d_%H-%M-%S' );
Run the vardoc full tests. init, apply, then cleanup.
cd docroot/profiles/vardoc;
../../../bin/behat tests/features/vardoc --format pretty --out std --format html --out tests/reports/vardoc-apply-tests-report-$( date '+%Y-%m-%d_%H-%M-%S' );
We could run behat tests with this set Go to [ PROJECT_DIR_NAME/docroot/profiles/vardoc ] in the terminal then you could run the following command:
$ ../../../bin/behat tests/features/vardoc
Then you will be able to open the full report for the automated test in a web browser at the following path: [ PROJECT_DIR_NAME/docroot/profiles/vardoc/tests/reports ]