test-kitchen 1.23.2 → 1.23.3

data/docs/content/docs/getting-started/09-writing-test.md

@@ -0,0 +1,49 @@
+---
+title: Writing a Test
+slug: writing-test
+menu:
+  docs:
+    parent: getting_started
+    weight: 90
+---
+
+Being able to manually verify the Chef run is great but it would be even better if we had an executable test that would fail if our assumptions were ever proven to be false. Remember how we manually verified that Git was installed in the previous section? Seems like a pretty decent first test to me!
+
+Kitchen presumes you want to test things and supports a variety of different frameworks for doing so. For the purpose of our guide we're going to use a framework called InSpec which kitchen consumes via the `kitchen-inspec` plugin. For more information on available testing frameworks check out [Verifiers](/docs/verifiers)
+
+The cookbook skeleton already has conveniently created a test for you at `test/integration/default/default_test.rb`. Open this file in your editor and edit to match the following content:
+
+~~~
+# # encoding: utf-8
+
+describe package('git') do
+  it { should be_installed }
+end
+~~~
+
+Why `test/integration/default/default_test.rb`? Let's take a look again at our `.kitchen.yml`:
+
+~~~
+# relevant sections of config
+---
+verifier:
+  name: inspec
+
+suites:
+  - name: default
+    run_list:
+      - recipe[git_cookbook::default]
+    verifier:
+      inspec_tests:
+        - test/integration/default
+    attributes:
+~~~
+
+Here we are telling the verifier with the `inspec_tests` key to look in this directory. In our example we are pointing to a local directory but `kitchen-inspec` supports [remote locations](https://github.com/chef/kitchen-inspec#use-remote-inspec-profiles) such as git repositories or even a Chef Automate server.
+
+Can you guess what this does even if you haven't seen an InSpec test before? If not, then take a look at InSpec's [package resource documentation](http://inspec.io/docs/reference/resources/package/). Otherwise your friends in the [Chef Community Slack](http://community-slack.chef.io/) should be able to help.
+
+<div class="sidebar--footer">
+<a class="button primary-cta" href="/docs/getting-started/running-verify">Next - kitchen verify</a>
+<a class="sidebar--footer--back" href="/docs/getting-started/manually-verifying">Back to previous step</a>
+</div>

data/docs/content/docs/getting-started/10-running-verify.md

@@ -0,0 +1,120 @@
+---
+title: kitchen verify
+slug: running-verify
+menu:
+  docs:
+    parent: getting_started
+    weight: 100
+---
+
+In order to execute our test, we use the command `kitchen verify`:
+
+~~~
+$ kitchen verify default-ubuntu-1604
+-----> Starting Kitchen (v1.23.2)
+-----> Setting up <default-ubuntu-1604>...
+       Finished setting up <default-ubuntu-1604> (0m0.00s).
+-----> Verifying <default-ubuntu-1604>...
+       Loaded tests from {:path=>".Users.cheeseplus.focus.git_cookbook.test.integration.default"}
+
+Profile: tests from {:path=>"/Users/cheeseplus/focus/git_cookbook/test/integration/default"} (tests from {:path=>".Users.cheeseplus.focus.git_cookbook.test.integration.default"})
+Version: (not specified)
+Target:  ssh://vagrant@127.0.0.1:2222
+
+  System Package git
+     ✔  should be installed
+
+Test Summary: 1 successful, 0 failures, 0 skipped
+       Finished verifying <default-ubuntu-1604> (0m0.28s).
+-----> Kitchen is finished. (0m3.33s)
+~~~
+
+A few things of note from the output above:
+
+* `Verifying <default-ubuntu-1604>` output corresponds to the start of the **Verify Action**
+* `✔  git should be installed` is output from the InSpec test
+
+
+<div class="callout">
+<h3 class="callout--title">Pro Tip</h3>
+If using a Bash-like shell, <code>echo $?</code> is will print the exit code of the last run shell command. This would show that the <code>kitchen verify</code> command exited cleanly with <code>0</code>.
+</div>
+
+Let's check the status of our instance again:
+
+~~~
+$ kitchen list
+Instance             Driver   Provisioner  Verifier  Transport  Last Action  Last Error
+default-ubuntu-1604  Vagrant  ChefZero     Inspec    Ssh        Verified     <None>
+~~~
+
+So what would a failing test look like? Let's see. Open `test/integration/default/default_test.rb` and edit the test so that we're testing that git is _not_ installed:
+
+~~~
+describe package('git') do
+  it { should_not be_installed }
+end
+~~~
+
+And re-run the **verify** subcommand:
+
+~~~
+$ kitchen verify default-ubuntu-1604
+-----> Starting Kitchen (v1.23.2)
+-----> Verifying <default-ubuntu-1604>...
+       Loaded tests from {:path=>".Users.cheeseplus.focus.git_cookbook.test.integration.default"}
+
+Profile: tests from {:path=>"/Users/cheeseplus/focus/git_cookbook/test/integration/default"} (tests from {:path=>".Users.cheeseplus.focus.git_cookbook.test.integration.default"})
+Version: (not specified)
+Target:  ssh://vagrant@127.0.0.1:2222
+
+  System Package git
+     ×  should not be installed
+     expected System Package git not to be installed
+
+Test Summary: 0 successful, 1 failure, 0 skipped
+>>>>>> ------Exception-------
+>>>>>> Class: Kitchen::ActionFailed
+>>>>>> Message: 1 actions failed.
+>>>>>>     Verify failed on instance <default-ubuntu-1604>.  Please see .kitchen/logs/default-ubuntu-1604.log for more details
+>>>>>> ----------------------
+>>>>>> Please see .kitchen/logs/kitchen.log for more details
+>>>>>> Also try running `kitchen diagnose --all` for configuration
+~~~
+
+Unsurprisingly, we get the message `×  should not be installed` and kitchen throws an exception.
+
+Let's revert our forced failure:
+
+~~~
+describe package('git') do
+  it { should be_installed }
+end
+~~~
+
+Then verify our revert:
+
+~~~
+$ kitchen verify default-ubuntu-1604
+-----> Starting Kitchen (v1.23.2)
+-----> Verifying <default-ubuntu-1604>...
+       Loaded tests from {:path=>".Users.cheeseplus.focus.git_cookbook.test.integration.default"}
+
+Profile: tests from {:path=>"/Users/cheeseplus/focus/git_cookbook/test/integration/default"} (tests from {:path=>".Users.cheeseplus.focus.git_cookbook.test.integration.default"})
+Version: (not specified)
+Target:  ssh://vagrant@127.0.0.1:2222
+
+  System Package git
+     ✔  should be installed
+
+Test Summary: 1 successful, 0 failures, 0 skipped
+       Finished verifying <default-ubuntu-1604> (0m0.32s).
+-----> Kitchen is finished. (0m3.06s)
+~~~
+
+One of the advantages of `kitchen-inspec` is that the InSpec tests are executed from the host over the transport (SSH or WinRM) to the instance. No tests need to be uploaded to the instance itself.
+
+<div class="sidebar--footer">
+<a class="button primary-cta" href="/docs/getting-started/running-test">Next - kitchen test</a>
+<a class="sidebar--footer--back" href="/docs/getting-started/writing-test">Back to previous step</a>
+</div>

data/docs/content/docs/getting-started/11-running-test.md

@@ -0,0 +1,168 @@
+---
+title: kitchen test
+slug: running-test
+menu:
+  docs:
+    parent: getting_started
+    weight: 110
+---
+
+Now it's time to introduce to the **test** meta-action which helps you automate all the previous actions so far into one command. Checking `kitchen list`, the "Last Action" of our instance should be "Verified". With this in mind, let's run `kitchen test`:
+
+~~~
+-----> Starting Kitchen (v1.23.2)
+-----> Cleaning up any prior instances of <default-ubuntu-1604>
+-----> Destroying <default-ubuntu-1604>...
+       ==> default: Forcing shutdown of VM...
+       ==> default: Destroying VM and associated drives...
+       Vagrant instance <default-ubuntu-1604> destroyed.
+       Finished destroying <default-ubuntu-1604> (0m5.56s).
+-----> Testing <default-ubuntu-1604>
+-----> Creating <default-ubuntu-1604>...
+       Bringing machine 'default' up with 'virtualbox' provider...
+       ==> default: Importing base box 'bento/ubuntu-16.04'...
+       ==> default: Matching MAC address for NAT networking...
+       ==> default: Checking if box 'bento/ubuntu-16.04' is up to date...
+       ==> default: Setting the name of the VM: default-ubuntu-1604_default_1537638619562_49760
+       ==> default: Clearing any previously set network interfaces...
+       ==> default: Preparing network interfaces based on configuration...
+           default: Adapter 1: nat
+       ==> default: Forwarding ports...
+           default: 22 (guest) => 2222 (host) (adapter 1)
+       ==> default: Booting VM...
+       ==> default: Waiting for machine to boot. This may take a few minutes...
+           default: SSH address: 127.0.0.1:2222
+           default: SSH username: vagrant
+           default: SSH auth method: private key
+           default:
+           default: Vagrant insecure key detected. Vagrant will automatically replace
+           default: this with a newly generated keypair for better security.
+           default:
+           default: Inserting generated public key within guest...
+           default: Removing insecure key from the guest if it's present...
+           default: Key inserted! Disconnecting and reconnecting using new SSH key...
+       ==> default: Machine booted and ready!
+       ==> default: Checking for guest additions in VM...
+       ==> default: Setting hostname...
+       ==> default: Mounting shared folders...
+           default: /tmp/omnibus/cache => /Users/cheeseplus/.kitchen/cache
+       ==> default: Machine not provisioned because `--no-provision` is specified.
+       [SSH] Established
+       Vagrant instance <default-ubuntu-1604> created.
+       Finished creating <default-ubuntu-1604> (0m36.40s).
+-----> Converging <default-ubuntu-1604>...
+       Preparing files for transfer
+       Preparing dna.json
+       Resolving cookbook dependencies with Berkshelf 7.0.6...
+       Removing non-cookbook files before transfer
+       Preparing validation.pem
+       Preparing client.rb
+-----> Installing Chef Omnibus (install only if missing)
+       Downloading https://omnitruck.chef.io/install.sh to file /tmp/install.sh
+       Trying wget...
+       Download complete.
+       ubuntu 16.04 x86_64
+       Getting information for chef stable  for ubuntu...
+       downloading https://omnitruck.chef.io/stable/chef/metadata?v=&p=ubuntu&pv=16.04&m=x86_64
+         to file /tmp/install.sh.1561/metadata.txt
+       Trying wget...
+       Download complete.
+       ubuntu 16.04 x86_64
+       Getting information for chef stable  for ubuntu...
+       downloading https://omnitruck.chef.io/stable/chef/metadata?v=&p=ubuntu&pv=16.04&m=x86_64
+         to file /tmp/install.sh.1561/metadata.txt
+       trying wget...
+       sha1     174eb82ebe2eddc9c370487de6c124907f6d2f3a
+       sha256   70ce695d2bf9fb01279a726148c0600544f1cd431642fa98d6696ef4c1dfc3c9
+       url      https://packages.chef.io/files/stable/chef/14.5.27/ubuntu/16.04/chef_14.5.27-1_amd64.deb
+       version  14.5.27
+       downloaded metadata file looks valid...
+       /tmp/omnibus/cache/chef_14.5.27-1_amd64.deb exists
+       Comparing checksum with sha256sum...
+
+       WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING
+
+       You are installing an omnibus package without a version pin.  If you are installing
+       on production servers via an automated process this is DANGEROUS and you will
+       be upgraded without warning on new releases, even to new major releases.
+       Letting the version float is only appropriate in desktop, test, development or
+       CI/CD environments.
+
+       WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING
+
+       Installing chef
+       installing with dpkg...
+       Selecting previously unselected package chef.
+(Reading database ... 38378 files and directories currently installed.)
+       Preparing to unpack .../cache/chef_14.5.27-1_amd64.deb ...
+       Unpacking chef (14.5.27-1) ...
+       Setting up chef (14.5.27-1) ...
+       Thank you for installing Chef!
+       Transferring files to <default-ubuntu-1604>
+       Starting Chef Client, version 14.5.27
+       Creating a new client identity for default-ubuntu-1604 using the validator key.
+       resolving cookbooks for run list: ["git_cookbook::default"]
+       Synchronizing Cookbooks:
+         - git_cookbook (0.1.0)
+       Installing Cookbook Gems:
+       Compiling Cookbooks...
+       Converging 1 resources
+       Recipe: git_cookbook::default
+         * apt_package[git] action install (up to date)
+
+       Running handlers:
+       Running handlers complete
+       Chef Client finished, 0/1 resources updated in 01 seconds
+       Downloading files from <default-ubuntu-1604>
+       Finished converging <default-ubuntu-1604> (0m22.87s).
+-----> Setting up <default-ubuntu-1604>...
+       Finished setting up <default-ubuntu-1604> (0m0.00s).
+-----> Verifying <default-ubuntu-1604>...
+       Loaded tests from {:path=>".Users.cheeseplus.focus.git_cookbook.test.integration.default"}
+
+Profile: tests from {:path=>"/Users/cheeseplus/focus/git_cookbook/test/integration/default"} (tests from {:path=>".Users.cheeseplus.focus.git_cookbook.test.integration.default"})
+Version: (not specified)
+Target:  ssh://vagrant@127.0.0.1:2222
+
+  System Package git
+     ✔  should be installed
+
+Test Summary: 1 successful, 0 failures, 0 skipped
+       Finished verifying <default-ubuntu-1604> (0m0.29s).
+-----> Destroying <default-ubuntu-1604>...
+       ==> default: Forcing shutdown of VM...
+       ==> default: Destroying VM and associated drives...
+       Vagrant instance <default-ubuntu-1604> destroyed.
+       Finished destroying <default-ubuntu-1604> (0m5.61s).
+       Finished testing <default-ubuntu-1604> (1m10.75s).
+-----> Kitchen is finished. (1m13.21s)
+~~~
+
+There's only one remaining action left that needs a mention: the **Destroy Action** which as one might expect, destroys the instance. With this in mind, here's what kitchen is doing in the **Test Action**:
+
+1. Destroys the instance if it exists
+2. Creates the instance
+3. Converges the instance
+4. Verifies the instance with InSpec
+5. Destroys the instance
+
+A few details with regards to test:
+
+* Kitchen will abort the run on the instance at the first sign of trouble. This means that if your Chef run fails then InSpec won't be run and the instance won't be destroyed. This gives you a chance to inspect the state of the instance and fix any issues.
+* The behavior of the final destroy action can be overridden if desired. Check out the CLI help for the `--destroy` flag using `kitchen help test`.
+* The primary use case in mind for this meta-action is in a Continuous Integration environment or a command for developers to run before check in or after a fresh clone. If you're using this in your test-code-verify development cycle it's going to quickly become very slow and frustrating. You're better off running the **converge** and **verify** sub-commands in development and save the **test** sub-command when you need to verify the end-to-end run of your code.
+
+Finally, let's check the status of the instance:
+
+~~~
+$ kitchen list
+Instance             Driver   Provisioner  Verifier  Transport  Last Action    Last Error
+default-ubuntu-1604  Vagrant  ChefZero     Inspec    Ssh        <Not Created>  <None>
+~~~
+
+Back to square one.
+
+<div class="sidebar--footer">
+<a class="button primary-cta" href="/docs/getting-started/adding-platform">Next - Adding a Platform</a>
+<a class="sidebar--footer--back" href="/docs/getting-started/running-verify">Back to previous step</a>
+</div>

data/docs/content/docs/getting-started/12-adding-platform.md

@@ -0,0 +1,206 @@
+---
+title: Adding a Platform
+slug: adding-platform
+menu:
+  docs:
+    parent: getting_started
+    weight: 120
+---
+
+Now that we have Ubuntu working, let's add support for CentOS to our cookbook. This shouldn't be too bad. Open `.kitchen.yml` in your editor and the `centos-7` line to your platforms list so that it resembles:
+
+~~~
+---
+driver:
+  name: vagrant
+
+provisioner:
+  name: chef_zero
+
+verifier:
+  name: inspec
+
+platforms:
+  - name: ubuntu-16.04
+  - name: centos-7
+
+suites:
+  - name: default
+    run_list:
+      - recipe[git_cookbook::default]
+    verifier:
+      inspec_tests:
+        - test/integration/default
+    attributes:
+~~~
+
+Now let's check the status of our instances:
+
+~~~
+$ kitchen list
+Instance             Driver   Provisioner  Verifier  Transport  Last Action    Last Error
+default-ubuntu-1604  Vagrant  ChefZero     Inspec    Ssh        <Not Created>  <None>
+default-centos-7     Vagrant  ChefZero     Inspec    Ssh        <Not Created>  <None>
+~~~
+
+We're going to use two shortcuts in the next command:
+
+* Each instance has a simple state machine that tracks where it is in its lifecycle. Given its current state and the desired state, the instance is smart enough to run all actions in between current and desired.
+* Any `kitchen` subcommand that takes an instance name as an argument can take a Ruby regular expression that will be used to glob a list of instances together. This means that `kitchen test ubuntu` would run the **test** action on all instances that had `ubuntu` in their name. Note that the **list** subcommand also takes the regex-globbing argument so feel free to experiment there.
+
+In our next example we'll select the `default-centos-7` instance with simply `7` and will take it from uncreated to verified in one command.
+
+Let's see how CentOS runs our cookbook:
+
+~~~
+$ kitchen verify 7
+-----> Starting Kitchen (v1.23.2)
+-----> Creating <default-centos-7>...
+       Bringing machine 'default' up with 'virtualbox' provider...
+       ==> default: Box 'bento/centos-7' could not be found. Attempting to find and install...
+           default: Box Provider: virtualbox
+           default: Box Version: >= 0
+       ==> default: Loading metadata for box 'bento/centos-7'
+           default: URL: https://vagrantcloud.com/bento/centos-7
+       ==> default: Adding box 'bento/centos-7' (v201808.24.0) for provider: virtualbox
+           default: Downloading: https://vagrantcloud.com/bento/boxes/centos-7/versions/201808.24.0/providers/virtualbox.box
+==> default: Successfully added box 'bento/centos-7' (v201808.24.0) for 'virtualbox'!
+       ==> default: Importing base box 'bento/centos-7'...
+==> default: Matching MAC address for NAT networking...
+       ==> default: Checking if box 'bento/centos-7' is up to date...
+       ==> default: Setting the name of the VM: default-centos-7_default_1537639719415_97528
+       ==> default: Clearing any previously set network interfaces...
+       ==> default: Preparing network interfaces based on configuration...
+           default: Adapter 1: nat
+       ==> default: Forwarding ports...
+           default: 22 (guest) => 2222 (host) (adapter 1)
+       ==> default: Booting VM...
+       ==> default: Waiting for machine to boot. This may take a few minutes...
+           default: SSH address: 127.0.0.1:2222
+           default: SSH username: vagrant
+           default: SSH auth method: private key
+           default: Warning: Connection reset. Retrying...
+           default:
+           default: Vagrant insecure key detected. Vagrant will automatically replace
+           default: this with a newly generated keypair for better security.
+           default:
+           default: Inserting generated public key within guest...
+           default: Removing insecure key from the guest if it's present...
+           default: Key inserted! Disconnecting and reconnecting using new SSH key...
+       ==> default: Machine booted and ready!
+       ==> default: Checking for guest additions in VM...
+       ==> default: Setting hostname...
+       ==> default: Mounting shared folders...
+           default: /tmp/omnibus/cache => /Users/cheeseplus/.kitchen/cache
+       ==> default: Machine not provisioned because `--no-provision` is specified.
+       [SSH] Established
+       Vagrant instance <default-centos-7> created.
+       Finished creating <default-centos-7> (1m33.52s).
+-----> Converging <default-centos-7>...
+       Preparing files for transfer
+       Preparing dna.json
+       Resolving cookbook dependencies with Berkshelf 7.0.6...
+       Removing non-cookbook files before transfer
+       Preparing validation.pem
+       Preparing client.rb
+-----> Installing Chef Omnibus (install only if missing)
+       Downloading https://omnitruck.chef.io/install.sh to file /tmp/install.sh
+       Trying wget...
+       Download complete.
+       el 7 x86_64
+       Getting information for chef stable  for el...
+       downloading https://omnitruck.chef.io/stable/chef/metadata?v=&p=el&pv=7&m=x86_64
+         to file /tmp/install.sh.3219/metadata.txt
+       trying wget...
+       sha1     47d9cc239e87a6f4eb3b7d15de6bb68aa66f993f
+       sha256   43e9a1ebe8aec723bf4e8503530348d2121fc6ee5a3b035ac4daf87f1712f5b4
+       url      https://packages.chef.io/files/stable/chef/14.5.27/el/7/chef-14.5.27-1.el7.x86_64.rpm
+       version  14.5.27
+       downloaded metadata file looks valid...
+       /tmp/omnibus/cache/chef-14.5.27-1.el7.x86_64.rpm exists
+       Comparing checksum with sha256sum...
+
+       WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING
+
+       You are installing an omnibus package without a version pin.  If you are installing
+       on production servers via an automated process this is DANGEROUS and you will
+       be upgraded without warning on new releases, even to new major releases.
+       Letting the version float is only appropriate in desktop, test, development or
+       CI/CD environments.
+
+       WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING
+
+       Installing chef
+       installing with rpm...
+       warning: /tmp/omnibus/cache/chef-14.5.27-1.el7.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 83ef826a: NOKEY
+       Preparing...                          ################################# [100%]
+       Updating / installing...
+          1:chef-14.5.27-1.el7               ################################# [100%]
+       Thank you for installing Chef!
+       Transferring files to <default-centos-7>
+       Starting Chef Client, version 14.5.27
+       Creating a new client identity for default-centos-7 using the validator key.
+       resolving cookbooks for run list: ["git_cookbook::default"]
+       Synchronizing Cookbooks:
+         - git_cookbook (0.1.0)
+       Installing Cookbook Gems:
+       Compiling Cookbooks...
+       Converging 1 resources
+       Recipe: git_cookbook::default
+         * yum_package[git] action install
+           - install version 0:1.8.3.1-14.el7_5.x86_64 of package git
+
+       Running handlers:
+       Running handlers complete
+       Chef Client finished, 1/1 resources updated in 14 seconds
+       Downloading files from <default-centos-7>
+       Finished converging <default-centos-7> (0m35.28s).
+-----> Setting up <default-centos-7>...
+       Finished setting up <default-centos-7> (0m0.00s).
+-----> Verifying <default-centos-7>...
+       Loaded tests from {:path=>".Users.cheeseplus.focus.git_cookbook.test.integration.default"}
+
+Profile: tests from {:path=>"/Users/cheeseplus/focus/git_cookbook/test/integration/default"} (tests from {:path=>".Users.cheeseplus.focus.git_cookbook.test.integration.default"})
+Version: (not specified)
+Target:  ssh://vagrant@127.0.0.1:2222
+
+  System Package git
+     ✔  should be installed
+
+Test Summary: 1 successful, 0 failures, 0 skipped
+       Finished verifying <default-centos-7> (0m0.65s).
+-----> Kitchen is finished. (2m12.04s)
+~~~
+
+Nice! We've verified that our cookbook works on Ubuntu 16.04 and CentOS 7. Since the CentOS instance is no longer needed, let's destroy it for now:
+
+~~~
+$ kitchen destroy
+-----> Starting Kitchen (v1.23.2)
+-----> Destroying <default-ubuntu-1604>...
+       Finished destroying <default-ubuntu-1604> (0m0.00s).
+-----> Destroying <default-centos-7>...
+       ==> default: Forcing shutdown of VM...
+       ==> default: Destroying VM and associated drives...
+       Vagrant instance <default-centos-7> destroyed.
+       Finished destroying <default-centos-7> (0m5.89s).
+-----> Kitchen is finished. (0m8.62s)
+~~~
+
+Interesting. Kitchen tried to destroy both instances, one that was created and the other that was not. Which brings us to another tip with the `kitchen` command:
+
+> **Any `kitchen` subcommand without an instance argument will apply to all instances.**
+
+Let's make sure everything has been destroyed:
+
+~~~
+$ kitchen list
+Instance             Driver   Provisioner  Verifier  Transport  Last Action    Last Error
+default-ubuntu-1604  Vagrant  ChefZero     Inspec    Ssh        <Not Created>  <None>
+default-centos-7     Vagrant  ChefZero     Inspec    Ssh        <Not Created>  <None>
+~~~
+
+<div class="sidebar--footer">
+<a class="button primary-cta" href="/docs/getting-started/adding-feature">Next - Adding a Feature</a>
+<a class="sidebar--footer--back" href="/docs/getting-started/running-test">Back to previous step</a>
+</div>