3. Cucumber features “Feature” in cucumber is supposed to describe a single feature which is analog with “test group”/”test class” in standard Java world. A feature includes one or more scenarios. A scenario can be represented as a “test case” or a ”test method“ in standard Java world. The code of a cucumber feature need […]
2. How to install cucumber in Eclipse To start using cucumber in eclipse we need to install few things: First of all eclipse and Java Development Kit (JDK) need to be installed on the computer. Ones eclipse finished with the installation we are able to install “Cucumber Eclipse Plugin” with eclipse built-in plugin installation tool. […]
New Year. New Resolution(s). If you haven’t started yet to work on new skills, it is the right period to do it. (it is never late anyway, but sooner is better) Some holidays are over, some will just arrive. You have already started thinking about “upgrade” yourself to a “bigger”, smarter, more valuable you. Good […]
One of the key elements of the functional programing is that we can treat functions as objects. In a typical functional language we can have a variable with type of function. The benefits are that we can use functions as: parameter return type variable The type Function in Java is interface with one abstract method. […]
Programming language Java doesn’t allow multiple inheritances. Java uses interfaces to simulate multiple inheritances without importing its disadvantages. The cost of this is that method implementation was not possible in interfaces until JDK 8. JDK 8 contains a new feature which allows us to create default implementation for interface methods. Simply just add keyword “default” […]
We recently faced with an Selenium’s sendKeys() method issue which is related to the page which was made in Angular 1.5.8 (Most likely the same issue can be discovered in different versions). In most of the cases, the input field filled by sendKeys() method will contain just part of the desired text. Most often you […]
Sometimes the usual test log and screenshot is not enough to find the reason of the failed test case. Especially when the test case occasionally fails in special circumstances and it is really hard to reproduce. For this reason, we need to collect for each fail as much information as possible. One possible source of information is the console output of the browser.
The Gherkin language provide us with lot of ambiguous commands that help us write steps faster and code less. Beside the default steps you can always add your own steps and write background code for additional re-usability and handling. More about this on later blog following the Behat BDD development. To list out the default […]
Continuing on my previous post about setting up a Behat test environment on Windows 10 now we will create some tests to see how the setup is working. These are some basic tests, as we are learning together.For running test we need to create a “behat.yml” file which Behat use as configuration file by default. […]
We had an issue with hibernate connections failed to close. We used separated connections for each Dao and all of them stayed open even we called session.close() in after method for each used Dao and checked that they were really executed. The connections have died 2h after the test run, for each test we left open 5-10 connection and because the connection limit to the DB was really small (100 connection) we were unable to run tests as often as we wished.
Useful information about connection kill can be found here.
Recent Comments