Testopia [Over the wall]

While we doing a test run some times we met some bugs related to other products. (mm.. other means not related to the testing product. Say SRS) Then what we are doing is initiate a bug for it. (Yes.. that's the normal procedure and it will track to closure) But other than that to get the maximum from Testopia we can create a test case for that bug. The Testopia extension (for Bugzilla...) provide a link "Create a test case" at the top of the bug page. 

We need to select the product. Then need to set the Priority, Category and Status. Testopia load the bug description to the Action field. From that we can "cut" and "copy" the "Setup" and "Expected Results" fields.

Advantage.

1. The method of finding the bug will never dismiss. Each and every test run we can check whether the same bug occurs again due to another change.
2. If the same bug occurs again the tester don't need to memorize whether this has a reported bug. Cause Testopia care about it. 

Report a bug.

As i mention earlier Testopia is a Test case management system. While running a test run we check the product met the requirements. If it is yes, the test case will pass. Else fails. So we have to track it in the next version. Because of the we report a bug in Bugzilla. Testopia was designed to bind those bugs with the particular test case. 

When reporting a bug through the testopia it automatically generates Product name, Component and Version. Other than that we have to set the platform, OS, bug status, title and description. Among those things title and the description are the most important things. 

Title - Should be a single line. But need to describe the bug very briefly.

Description - Should consist of three major parts with optional part. 

1. Steps to reproduce. - It should be clear for any developer. Not only for the implementor.
2. Actual outcome - Clearly mention what you see/get.
3. Expected outcome - If the bug reporting for a test case clearly mention the requirement. 
4. Position of the requirement in the SRS. (Optional) - SRS name, Version and the requirement number or  page number with line number.

Testopia

Don't say it as "Test" --  "Opia". There is no meaning. But using that words can understand that is a something related to testing. I have familier with Bugzilla. This Testopia is something like a plugin working on the bugzilla. As we know we use bugzilla for report bugs of a program while doing the testing. This Testopia helps to organize test cases. (mmm... not the code related test cases. Im talking about SRS test cases written by a QAE)

So no need to write the test cases on excel sheets anymore. So any one can view the test cases easily related to the particular projects.

The other important thing is we can create test runs. That means we can select particular test cases and create a test run for a project. So while doing the test run it automatically show the progress in the dash board. And also while doing the test run we can report bugs for failed test cases. (.. Nice,, isn't it.)

[Ok.. i know your question... ;)     Its coming soon on My Road....  How to install Testopia]

Login without a password.

ssh-keygen

hmm... This is use to generate the private and public keys to authenticate ssh. Yesterday i had to use this command to generate a public key as per our network admins request. [You are wrong... he's a good one..! ;)] He told me that i don't need to type the password each and every time when i'm connecting to the GIT. [mm...  it's a version control system like SVN.]

Fortunately it light up a new idea. [yes... new for me.. :D] 

Ok.. These are the steps.

1) $> ssh-keygen -t rsa         : Generate private/public rsa keys.

         Enter file in which to save the key (/home/kumudu/.ssh/id_ras) : <return>

         Enter passphrase (empty for no passphrase):  <return>

         Enter same passphrase again:  <return>

         Your identification has been saved in /home/kumudu/.ssh/id_rsa.

         Your public key has been saved in /home/kumudu/.ssh/id_rsa.pub.

         The key fingerprint is:

         67:5b:54:e8:1f:eb:46:7a:00:3b:72:33:9a:cc:d3:32 kumudu@hmslp030

         The key's randomart image is:

         +--[ RSA 2048]----+

          |                          ..  |

          |                         ..   |

          |                        ..    |

          |                       ... .  |

          |                 S oo.. o |

          |                 .o*o. +  |

          |                o *.+ =   |

          |                   E . . +  |

          |                    +   o   |

         +-------------------+

Ok... Your public key is in /.ssh/id_rsa.pub file. 

2) $> ssh-add      :  This will add the generated keys to ssh. (If you miss this you will get a message like "Agent admitted failure to sign using the key." while connecting to the remote machine.  [I spend lot of time to find this...])

3) Copy that public key onto remote machines' .ssh/authorized_keys file. (mmm... normally this file doesn't exist. Just create a new file named "authorized_keys" in .ssh folder and copy the public key into it.)

4) Then make the file permission as follows. (Actually i don't know the exact reason for this. Without this permission ssh refuse to use the key)

       $> chmod 600 .ssh/authorized_keys

5) $> ssh <profile_name>@<remote_host>

hmmm... thats all.. I tested it on fedora machine and ubuntu machine. 

Advantages.

• If someone ask for login to your machine through ssh, simply ask him to send the rsa public key. Then add it to your autherized_keys file. [you don't need to expose your password]

• The other person don't need to remember your password. [yes.. yes... only the ip ;)]

• If you want to stop him just remove the key... 

Selenium

Yesterday i thought to find a test tool. My requirement was to find a tool for test web pages. Also it should be a simple one. (Yes... i don't like to jump at once..) How ever i found "Canoo web test", "Selenium", "Watin" and "Watir" as popular test tools. But Selenium is familiar for me. Cause there was a simulator called as selenium which i was used 3 years ago. (http://www.seleniumsoftware.com/downloads.html) 

SeleniumHQ (Web application testing tool) http://seleniumhq.org/

It has lot of tools. Selenium 1, Selenium 2, Selenium IDE, Selenium Grid like wise. As per the introduction this Selenium IDE is the easiest tool to learn. (Woww.. it can plug in to firefox. )

It has a feature called record. As a beginner i feel it was very attractive feature. We can record what we do on a particular web page and rerun it. (Yes... it generates all the commands automatically when we running the trail)

to be cont....