Latest Posts

TestLink – Test Management Tool : A Brief Description

What is TestLink?

TestLink is one of the most popular web-based and open source test management tools that facilitates software quality assurance. It supports both manual and automated execution of test cases. It is developed and maintained by Teamtest. The platform offers support for test cases, test suites, test plans, test projects and user management, as well as various reports and statistics.

With this tool, the testers can generate Test Report and Test Plan Documents within a minute. It supports the generation of Test reports in MS Word, Excel and HTML formats.

Features of TestLink

  1. Testing coverage
    – Black Box Testing

    – Functional/ Manual Testing
    – Automation Testing
    – Agile Testing and Traditional Testing
  2. Organizing, Managing and Tracking Feature
    – TestLink tool creates, centralizes, organizes and manages test cases very effectively and efficiently.
    – Test cases are organized in hierarchical structure (tree menu)
    – It can share test case repository across different projects, releases and sprints.
    – It supports run and re-run of test execution suites and captures step-by-step test execution history with detailed explanation.
    – It supports test run specific configuration and parameters.
  3. Reports/Charts Generation
    – It supports test case and test execution reports.
    – Requirement and traceability reports.
    – Defect reports.
    – Export of documentation to HTML, MS Word and MS Excel is supported. And reports could be mailed directly from the tool
  4. Integration
    – TestLink supports numerous add-ins to connect with different software to make work easy. Wide range of add-ins make it universal across the globe – JIRA, Mantis, Bugzilla, Trac, etc.
    – It also supports Rally and VersionOne integration.
  5. Customization
    – It supports to create and assign the user’s keyword.
    – It supports cloning the entire test case repository along the project setting.


TestLink – Dashboard Overview

After logging into TestLink, the UI (dashboard page) will look like the following screenshot. Of course, user has to be assigned to a project to get this view. Dashboard is customized by Admin. Based on the roles, admin can set the access of TestLink.

  • The tool bar icons, which is present at the top left corner of TestLink dashboard remains same across all the pages of TestLink. It contains My settings, Logout, Project, Test specification, Test execution, Test reports, User management, Events, Plugins.
  • From the left side menu- test project, test specification and other links can be accessed quickly.
  • From the right side menu- Test plan management option can be accessed quickly, for adding or managing a test plan.
  • On the top right corner of TestLink, there is test project drop-down to select test project easily.


Benefits of using TestLink : How it can help in testing process

  • It is an open source test management tool. That’s why the cost of license for paid tools can be saved.
  • It provides support for multiple projects as a single web application.
  • It allows very easy interface that allows to export and import of test cases. So, the test cases can be reused to save effort and time.
  • Test cases execution can be easily handled through XML-RPC.
  • TestLink tool permits an easy filtration of test cases. Test cases can be filtered through version, keywords, and Test Case ID.
  • TestLink allows to create multiple users in the system and allows to assign test cases to these users easily.
  • TestLink tool not only allows to create multiple users but also it can provide credentials to these multiple users with the assignment of various roles to them.
  • TestLink permits to generate test plan and test reports easily. Reports can be generated in various formats such as Excel, MS Word, and HTML formats.
  • TestLink tool can be integrated very easily with many defect management tools which may or may not be open source tools. Some of the defect management tools supported by integration are JIRA, MANTIS, BUGZILLA, TRAC, etc.

Points to be noted during the domain migration

Assessment of goals and objectives:

     Migrate the domain and hosting from one hosting provider to another provider.

     To reach my goal I faced some difficulties they are

  1. I didn’t know how to migrate public_html folder
  2. How to migrate database
  3. How to migrate mail server

     So I gathered clear concept how do this.

Identification of activities or areas needing additional effort:

      At first I need to know  where the domain we are transferring and how many

      time it’s needed.

      I had planned to transfer the domain into google domain and the time it  will be  taken         

      30 mints. But unfortunately I transferred the domain into another company

      so I needed more time to complete. So it’s very important where you 

      transferring and budget time.


Identification of effective activities or strategies:

  1. Plan the whole process.
  2. Budget time.
  3. Don’t mistake to create a cpanel account
  4. Test the mail server.


The Problem which I faced:

     When I transferred the  domain my mail server was not  working. All 

     mail are bounced back.


Points to be noted before domain migration:

     1. You shouldn’t longer your migration process.

     2. You should have clear concept where your  domain and hosting exist and where you want to    

          to transfer.


Steps for  hosting migration from one cpanel to another cpanel:

  1. Create an account according to previous cpanel account name.
  2. Check old hosting information
  3. Goto old Cpanel file manager compress the public_html and Download it.
  4. If you have another folder which you have to migrate just compress it download it.
  5. For database migration goto old cpanel click backupwizard click backup and click my sql database
  6. Download all database and goto new cpanel goto backupwizard and restore the database
  7. For mail server migration goto old cpanel and goto file manager and compress  mail and etc folder and download it.
  8. Now go  new cpanel and goto file manager and delete the mail and etc folder and upload mail and etc from older cpanel which you have downloaded.
  9. Now check the mail
  10. [warning] If your older and new cpanel account name are not same then you mail account will not be migrated
  11. Check mx record before domain transfer if its not created goto dns zone editor and add mx record .


Steps for domain migration from one provider to another:

      1. First check old domain provider details.

      2. Select  where you want to  transfer your domain and check how many days it needs

      3 . You may contact with your service  provider to know about how long it takes to transfer domain.

      4. First  unlock the domain from where it is transferred

      5. Goto where you want to transfer your domain it may be godaddy or inmotion or a2 hosting

         and go to transfer domain and give the authorization code

      6. Now pay the domain transfer charge

      7. When domain transfer will complete then add  nameserver .

      8. Now your old cpanel no longer exist

9. Check your mail server and add mx record if it’s not working contact your service provider.

Automated API testing with Postman


Hello everyone!! If your company maintains API for their products and you are a person who is responsible for testing the API endpoints then this blog is for you. This blog will be explaining how to get started with API testing using Postman. First we need to know a bit about API and Postman.

What is API?

API stands for Application Programming Interface.Its a set of blocks of code which are connected with different protocols to communicate with each other to make a connection between the Database and the GUI which makes a successful software.

There will be several endpoints which will access data from the database. The endpoints should be secured to make them fetch the right data for the right user. This is a tricky part for API. If any endpoint returns wrong data to the end users and the wrong data is something that end should never get access to, that can be a mess! So its really important to make it work correctly and tested properly.

Get started with API testing with Postman

To get started with API testing first you will need a tool. Postman is a good tool for this job. Download postman from here and install it to your machine. After the installation you will be asked to sign in. Use your google account or just register to postman. And you are ready to start the testing. 

This is a view from postman. 

1 –> Select the request type
2 –> Insert the request URL of your API endpoint
3 –> Its optional. If your API endpoint have parameters, add them here

Once you are done with these 3 points add value to header and body. Then hit Send button and the response will be seen here in the Response box. Check out the desired responses. If wrong/error response then the endpoint needs to be fixed.

This is how you work manually. To save your time its important to make your tests automated. For this its important to have all the endpoints available and documented properly. Make a Collection with the endpoints and sort them sequentially.

Now how to sort endpoints to a collection? Lets consider a login scenario. If you try to login to your mail, Postman generates a token with your username and password. With the token you can check your mails. there will be one endpoint to generate token with your login information and the other endpoint will use the token to fetch your mails to you. So the login endpoint must be the first one and then the endpoint which fetches the mails will be sorted next to it.

How do you make it automated? Here you will need to set up Environment for your tests.

Lets say you have generated a token with your login information:

postman token


And you will be using this token to check your mails with another endpoint. So what you do, you copy your token paste to the header of the next endpoint. This is the manual style. To make it automated you have to create an environment variable through Test Scripts:

save token to environment


Then the token gets saved in your environment. Now each time you need the token to check your mails and visit your profile you just call the variable with your endpoint and you get the response.

postman environment

Once you complete setting up your environment save it for the tests. Now go to the collection runner. There select a collection and corresponding environment. Click on Run Collection and the responses will be shown in the box at right side:

collection runner

Once its done the result will be saved automatically and the result can be imported for analysis. if any endpoint fails to fetch the correct information or gives any error response that result is marked as red and the successful one marked as green.

How to install ubuntu server and configure network

This blog will show how to install Ubuntu server on your machine and configure static network and finally how to install OpenSSH on your machine. This blog is divided into three parts:

1.Install Ubuntu server

2.Configure network

3.Install OpenSSH

Ubuntu server installation:

-You must have at least 2GB of free storage space.
-You must have either a DVD or a USB flash drive containing the version of Ubuntu Server you want to install.

Boot from DVD:
-Insert DVD in DVD drive should take you to the installation.

Boot from USB flash drive:
-Go to to download latest Ubuntu server.
-Download Ubuntu server.
-You can use Rufus to make your USB flash drive bootable. (

-Select your language:

-Select ‘Install Ubuntu Server’ on the next menu:
ubuntu installation

-Select your keyboard layout:

-Type your desired hostname. In terminal it will show username@hostname:~$

-Select your timezone and location:

-Select partition disk option.The simplest one is the, ‘Guided – use entire disk and set up LVM’.But you can do it manually, if you are installing alongside another operating system:

-For configuring tasksel choose ‘No automatic update’:

-Setup your username and password:

-Select whether you want to encrypt the hard drive or not. Selecting no is recommended.

-If you are using a proxy server, enter the details or leave it as blank:

-Select the softwares you want to install on your server. Press the space bar to select software, when finished press enter to continue. You can continue without installing any software and install it later if you wish:

-Ubuntu Server will now be installed. When complete, one final question asks for permission to install the GRUB boot loader. You should answer ‘Yes’:

-Congratulations! Installation is completed. You can now remove your DVD or USB flash drive:

-Restart your machine and begin enjoying Ubuntu Server.



Configure Networking:

-Login to your terminal and type ifconfig

username@hostname:~$ ifconfig

-Find your network interface card. Here red signed part is network interface card:

-To change ip address type sudo nano /etc/network/interfaces & edit this file and save:

username@hostname:~$ sudo nano /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eno16777736
iface eno16777736 inet static
address <your ip address>
network <your network>
broadcast <your broadcast address>
gateway <your gateway address>
dns-nameservers <your dns-nameserver addresses>

-Restart your network by typing sudo ifdown eno16777736 & then type sudo ifup eno16777736

username@hostname:~$ sudo ifdown eno16777736
username@hostname:~$ sudo ifup eno16777736

-If you want to check network state, you can use sudo ethtool eno16777736

username@hostname:~$ sudo ethtool eno16777736




Install OpenSSH:

-To install the OpenSSH client type: sudo apt install openssh-client

username@hostname:~$ sudo apt install openssh-client


-To install the OpenSSH server type: sudo apt install openssh-server

username@hostname:~$ sudo apt install openssh-server

Continue reading