Monday, June 8, 2015

The Process For Created Test Cases

1. Study on the software by given documentation like requirements, use cases, project plan, test plan, etc... If there is lack of documentation, work on software by executing exploratory testing and define as much as possible paths as a use case flow.

2. This step also may be called naming test cases in a given naming convention context. Identifying the test cases that represents the each path of the defined use cases is realized.

3. A detailing step follows naming. The test case is detailed by explaining the steps that user should do for test case execution. The "Cases" are made singular by adding several inputs.

A test case should contain following features at least;

  • Name
  • Description
  • Prerequisites (Like user must logged in etc...)
  • Steps

A test case step should contain;

  • Description
  • Input
  • Expected result

Saturday, April 11, 2015

R: a Programming Language

It is certain that R is a widely used statistical computing programming language. And it is promising for any other programming area. It is hard to change routines of programmers. That's why, many questions arise when a new thing comes up in the field, like;

  • Do I need to learn R?
  • Tell me what i can not do with other languages that i can do with R.
  • Why choose R?
  • Isn't it a statistical tool, why do i need to use it?
  • ...

There are many reasons to choose R. In this post i want to change the resistance of habits to choose R in some areas that you work on.

Friday, October 10, 2014

Spotify Agile Culture

Spotify engineering culture is detailed within these animated videos by Henrik Kniberg. Here is the fine best practice of agile methodologies. That is full of agile engineering in operation.

Wednesday, October 1, 2014

The 5 Gold Principles of Technical Meetings

These following principles are taken in a technical meeting based on a mistaken behaviours. They are all common but some how always ignored. They can be also reproducible...
  1. Do not attend to a meeting without agenda if possible. 

Friday, August 22, 2014

Do not search for Godaddy renewal coupon or promo code

A few days ago domains and shared hosting service where I bought from GoDaddy was about to expire. I was truely surprised when i logged in the system and saw the prices. Then I searched several times on the internet for coupon codes. But sadly, any of the coupons were not working for the renewals. After all, I did a thorough research for the alternatives. I consulted my colleagues on these issues. Though, I have no energy amd time to move on an alternative and solve the configuration issues. Finally I tagged GoDaddy on Twitter and said their price is too high and if they do not come up with more discount then I would try another alternative. They replied as follows.

Saturday, June 22, 2013

JIRA vs Redmine Comparison With Respect to Features and Specs

In this post, I will compare these two project issue tracker and team planner systems. Only, differences are detailed. Whole standard features which an issue tracker needs to perform is dismissed to see the exact discrepancies. Redmine and Jira supports many of the issue tracking requirements but you should decide one of them. This decision is a little bit tricky; using an opensource software or giving a licence fee.

First of all your requirements should be taken into account. The table below describes many of the features by comparing these systems. The feature details may help you to decide whether you need or not.

Monday, May 27, 2013

Upgrading Debian From Squeeze to Wheezy

Today PHP version 5.4 is needed some how on Debian Squeeze and after a little bit search on web I decided to update whole system to Debian Wheezy. By default, Debian Squeeze come up with PHP 5.3. Also it is possible to work with 5.4 on Squeeze but it needs much more effort to upgrade (I tried to compile PHP and failed). Anyway, Below procedure is successful to upgrade whole new Debian system.

Before starting, take your back-ups and your own risk :)