Test values matters.
Recently there was a bug I introduced that could be easily avoided if not poorly designed test values.
It was a pretty big refactor or core functionality. Scary, so I grabbed some people and did testing on my local environment, just to be sure everything works. I seemed so, great success!
I changed the application from one class to three with separated responsibilities, wrote some tests and use Travis-CI for continuous integration. Version 0.2.1 is available here.
Since the last post, the application changed a lot. When I had a little time I sat down and just coded. Changes are too small to wrote about separately, but now there are enough of them to do some summary 🙂
I’ve reorganized Photochooser a lot, changing names and directories. Also wrote my first test in Python, ugly one but still. The code is here.
A couple days ago my project was mentioned (it’s in Polish) by one of the contestants of GetNoticed competition. And it was a very strong motivational kick! Until then I was writing Photochooser just for myself, didn’t bother if anyone like it or not. But now, when I know someone looked at my project and found it potentially useful? It changes everything ? I really want to do it right, write useful application, pretty and tested code.
Thank you, Konrad!
This is a simple tutorial how to set up Selenium test with PHPUnit and phantomjs for easy and fast testing.
Today I wanted to learn something about Selenium. It’s very popular testing tool for any application that can be launched using a web browser, regardless of programming language or technology. I don’t know it very much, in fact, I know only how to set it up and write the simplest test 😉 But I want to share my today’s experiences because I cannot find any simple tutorial and had to glue together scripts, setting and libraries from all across the internet 😉
If you don’t like reading tutorials and want rather dig into example code I created the repository on GitHub where you can find everything I talk about here.