Running Behat Tests with Atom + Script

-

Atom is the cool new Text Editor / Source Code Editor from Github.
If you havent got it then head on over and check it out: https://atom.io/


Executing your Behat tests from inside Atom:

Open up the Atom preferences and search for and install the following packages:

Behat + Script




















Open up your Feature and bring up the 'Script' run options ( command + shift + i ).


  • Set "--ansi" in the 'Command Arguments' (shows pretty output)
  • Set your config and profile options in either the 'Command Arguments' or the 'Program Arguments'.
  • Set the grammar to be "Behat Feature" :
















Run the tests:




Comments

  1. CMTechSeptember 8, 2016 at 1:26 AM

    Thanks for sharing a valuable post and its really very helpful.

    PHP Web Development Brisbane

    ReplyDelete
  2. heelydavidSeptember 6, 2018 at 4:13 AM

    It is really a helpful blog to find some different source to add my knowledge. I came into aware of new professional blog and I am impressed with suggestions of author.
    web design for startups

    ReplyDelete

Post a Comment

Popular posts from this blog

Installing ReadyAPI on a Jenkins EC2 instance using X11

-
This includes the steps to get ReadyAPI (with licence) running on an AWS EC2 instance and the commands needed to run the Jenkins job  Login via SSH as ec2-user  Install Java x64 to /opt/jdk1.7.0_67/: sudo -s cd /opt wget http://download.oracle.com/otn-pub/java/jdk/7u79-b15/jdk-7u67-linux-x64.tar.gz tar zxvf jdk-7u67-linux-x64.tar.gz rm jdk-7u67-linux-x64.tar.gz Install X11 Virtual Frame Buffer (for running headless tests in Jenkins): sudo yum install xorg-x11-server-Xvfb Ensure X11 forwarding is enabled for SSH server: X11Forwarding yes Prepare the Ready! API install directory: sudo mkdir /data/app/ReadyAPI-1.3.1 sudo chown jenkins:jenkins /data/app/ReadyAPI-1.3.1 Reconnect the server using the user that will be using Ready! API (in this case "jenkins") with X11 forwarding enabled on the client: ssh -X -i ~/.ssh/AmazonKeys.pem jenkins@{jenkins URL} Download the latest version of Ready! API to the server:
Read more

Installing Testlink (Test Management Tool) on Ubuntu 12.04 (AWS EC2) with URL Rewrite

-
Image
After finding scattered offerings when it came to installing Testlink on Ubuntu i decided to document the process. Heres the rundown: Create a new micro instance (ubuntu 12.04) using the ‘select existing’ key pair, if you don’t have an existing create a new one and name it something memorable and download it to a folder that’s easy to get too. Create a security group and set the inbound ports to be the following: Go to your instance page and right click on the instance just created and choose “Connect” Select “Connect with a standalone SSH Client” copy the example in the popup window. Eg ·         ssh -i scottyg_au.pem  ubuntu@54.213.211.63 Open up terminal (Mac) or Cygwin (PC) Cd to the folder with the .pem file You need to modify the permissions on the .pem file, do this by running ·         chmod 400 ‘xx.pem’. Eg chmod 400 scottyg_au.pem Paste in the ‘ssh’ command into your terminal ssh -i scottyg_au.pem  u
Read more

Load testing ElasticSearch using ESRally and viewing the results in Kibana

-
Image
Run EsRally against an existing ElasticSeach index and save the results in Kibana Problem : Need to be able to write json queries and run these against an existing ES cluster Want to be able to view the EsRally results in a local ES instance The test run results to be available in Kibana Required to be installed: Docker Git 1. Get and build the ELK stack to store the test results against. Also defines the network so the docker containers can talk to each other. From your terminal/cmd: docker pull sebp/elk git clone  https://github.com/spujadas/elk-docker.git && cd elk-docker docker build -t sebp/elk . docker network create --subnet=172.18.0.0/16 elastic-esrally-network docker run --rm --net elastic-esrally-network --ip 172.18.0.5 -p 5601:5601 -p 9200:9200 -p 5044:5044 -it --name elk sebp/elk Local Kibana Local ElasticSearch ( Chrome plugin is recommended for viewing ES info) 2. Now we have ES and Kibana running its time to get ES rally sorte
Read more