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

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.