Scan Wifi from Terminal

There is a command line tool that allows you to work with the wireless connection on your Mac. The tool is very useful but by default hidden and not well documented.



Turn on/off and join

Let`s start a wifi scan and get some information

Note: If do not specify the interface, airport will use the first wifi interface on the system.

Easy way


The captured packets you will find as “/tmp/airportSniffXXXXXX.cap”.

Publish continuous integration status on Desktop

In one of my last tutorials, i show how to develop test tools for software tester with Python. Now i will show you, how to publish continuous integration status information for other team members like Scrum master, Product owner or Test manager.



If you don`t have Jenkins or Hudson running, search some public services with Google!

Example: inurl:8080 intitle:”Dashboard [Jenkins]”


Create a python script like this:

Now start GeekTool and create a new Geeklet. Drag a Shell Geeklet on you Desktop. Now insert values for name, size, set colors and so on and add the python script on “Command”.

Create Geeklet

… the script.

Geeklet Command

Thats it! Now you can export the Geeklet and share it with you team members. My current screen looks like:

Geeklet result

Simple ssh brute-force attack with Hydra

Test preparation

Install Hydra

Now create two files (or download anywhere)

Run tests

Create some content (by line) and start the ssh brute-force with Hydra.

If Hydra found something, the message looks like:

Note: for legal purposes only!

Create your own test application

A lot of software testers do have no or less development skills. They also have less skills to use commandline tools and need GUI applications. In addition, the test applications for the respective claims should be easy to use. This guide will show you how to easily deploy software testers the needed test tools. This is just an example, please feel free to expand it!


Let`s go

After create a new PyCharm project (with virtualenv), create 2 new empty files (requirements.txt, and import a icon. You can found icons (*.icns) on iconarchive for free.

application project files

Open the “requirements.txt” file and add Requests library.

Open the “” and add the following content.

For first test, run the application. If there are no issues – open the PyCharm terminal and run the following command.

Now you should see the generated file “” in the Project. Open the file and add the icon. The content should look like this:

Now execute the following command to build, for first test.

After some messages in terminal, your Project should show 2 new folders (build, dist). The alias mode (-A / –alias) instructs py2app to build an application, but it is not portable to other machines! You can open the Application in Finder or from terminal for your tests. If there are changes, just run the build-command again.

If everything is fine and your Application is ready for ship, run the following command.

Again the Application can be found on folder “dist”. The result should look like this:

example application

Have fun and be creative! Too ship the test application for Windows users, look at py2exe.

PyCharm with Virtualenv on Mac OS X

This guide shows you how to use PyCharm with virtualenv on Mac OS X.



First install we install Virtualenv and Virtualenvwrapper.

Now we start PyCharm to create new project.

PyCharm Virtualenv

After given the new name for the project on Location, select for Interpreter “Create VirtualEnv”.

PyCharm Create Virtualenv

Create Virtual Environment dialog box opens. Here type the name of the new virtual environment and specify the target directory for he new virtual environment on Location. Select one “Base interpreter” and if needed, select the check box “Inherit global site-packages”.

PyCharm Virtualenv Setup

Press “OK” button to apply changes and close the dialog box. After press the  “Create” button – PyCharm create the new project.


Speed up with VBoxManage

If you use Virtualbox, you can speed up your daily workflow with VBoxManage. This guide show some basic commands.



There ‘s more! If you are familiar with basic commands, read the help or user manual!

Install Jenkins with Puppet

As a software tester you need a test environment! The test environment should be soon as possible and without outside resources deployable. This guide shows you how to install Jenkins on Debian/Ubuntu with Puppet (Version 2.7.x).


If Puppet and Puppet-Lint are not installed:

The project looks like the following:


The first content we add is for “site.pp”. Here we include the “nodes.pp” and setup basic paths.

The next content is for second file “nodes.pp”. Here we create the case statement with the include for Jenkins class and a message (if OS is not supported).

As last step we create the content for “init.pp”.

Note: The space after “/etc /apt” on “update” and “source file” should removed! I made this just because of the security policies of my provider. They do not allow! 🙁


First we check the syntax with the puppet-lint. As software tester i think you always lint! 😉

Now we make some different “Dry-runs”.

With “–noop” nothing is really executed. The “–modulepath”, “–summarize” and “–debug” speaks for themselves.

the Final

Now the final, after the Puppet is ready you should able to connect to Jenkins.


Textmate with Puppet syntax highlighting

To enable syntax highlighting for puppet in textmate, follow this guide.


  • Textmate installed
  • Git installed (available with command line developer tools)


Create new folder on desktop

Go inside created folder and clone from Git repository

Move the “Puppet.tmbundle” file into specific folder and delete create folder on desktop

Now select a *.pp file and open with Textmate. In the Textmate dialog, select “Puppet” and “Install Bundle”.