My git workflow

Reading Time: 1 minute

git workflow

Note: please use git manual to get to know what each git command is actually doing. Divide feature on which you are working in short working deliverables. That means when you are done with your implementation and unit testing, you can merge to master branch and delete your small feature branch.

Clone repository (repository will be called repo furthermore in this wiki.)

mkdir ~/repos
cd repos
git clone
cd repo_name

Get latest code from remote

git status
git checkout master
git pull --rebase

Start working on feature_name. Be sure that feature scope is small as possible. We want your contribution to master as soon as possible!

git branch -a List of all repo branches, remote and local
git checkout -b feature_name Creates feature branch with name feature_name from master branch
git status
git push -u origin feature_name put feature branch to remote repo

Do your work in feature branch. Commit as much as possible.

git checkout feature_name To be sure that you are in appropriate feature branch.
git add .
git commit -m 'something useful and funny'

Send commits to remote repo branch

git rebase -i @{u}
git push -u origin feature_name

Code is ready for master after a lot of testing!

git checkout master
git merge --no-ff feature_name
grep -H -r '<<<<<<< HEAD' * | less -check for conflicts. Resolve them using your favourite editor
git commit -m 'merge from to'
git rebase -i @{u}
git push -u origin master
More on that topic could be found here.

Thank, you feature_name branch, we are done! Your life must be shorter than butterflies!

git push origin :feature_name
git branch -d feature_name
Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Notes on slide set for BBST Foundations lecture 3: Oracle.

Reading Time: 1 minute

This blog post is about my notes on slide set for BBST Foundations lecture 3: Oracle.
When I hear world Oracle, first thought that pop up in my mind is Matrix Reloaded scene with Oracle and Neo. Oracle is very important character, and so are testers oracles.
I started with required reading “Testing without a map” by Michael Bolton. Tester sometimes is doing exploratory testing in order to gather information for more detailed test strategy. Oracles (principle) and Heuristics (fallible guides) to Oracles. HICCUPPS heuristics with example.
Second read is “The essence of heuristics” by James Bach. Heuristics give a structure to our testing skill. Heuristics are not best practices.
“Using Heuristic Test Oracles” gave a good example how to use HICCUPPS heuristics.
I found “Definition of Engineering Method” by Koen on following link. Heuristics are important part of engineering method. This should be read by every engineer!
“On testing non-testable programs” lack of oracles is elaborated. Last two manuscripts were produced with typewriter, and it felt like reading ancient manuscripts about secrets of testing.
How we are good at creating and using created oracles, means how are we good at automated testing. I read Michaels blog post about test inputs and expected results. I found an issue in pdf, because although link was properly displayed, when I clicked on it, it pointed me to different blog post. Here is link once again. 

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Zagreb STC #12 report

Reading Time: 1 minute

Yesterday we had our testers meet up in ZIP, Zagreb incubator for startups. Little bit about Zagreb startup scene. In short, things are improving. There is now third generation of startups in there, and community of project partners is growing.
Our initial agenda, that is described here, was changed. Everybody from testing community is talking these days that context matters, so we acted on it. The reason was following. We started with Google hangout, on the other side was Zeljko in San Francisco. He is doing some cool testing  on Wikimedia international support. Tools that are involved are watir-webdriver and Sikuli. But be patient, Zeljko will very soon write about it on his blog.
When some members of ZIP herd that we were talking about browser automation, they immediately joined because they had a lot of questions about the topic. They are starting to use browser scripted testing.
After hangout, we continued discussion about the browser automation, and they were happy about it. I found out about new way of recruiting new developers, using REST API .
What is bothering  me is that only two testers showed up (including me). After two years of testers meet ups, Zagreb STC community is loosing its momentum. So fellow testers, please help with advice how to keep going. It seems that free beer and pizza are not enough.

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather