Linux configuration in our software testing lab

The following applications can be installed on windows and Linux partitions:

JMeter - regression testing tool(BeanShell library - bsh-xxxx.jar must be added)
DbVisualizer - database testing tool (connections to all Db added)
SQuirrel database testing tool (connections to all Db added)
SmartCVS (Automated Scripts and Custom Tasks repositories added and verified)

On the Linux partitions, the applications are installed at /usr/local/.
When a user created for you, please, add this user to “staff” group.
In order to do it, become a root, go to /etc/, open “group” file, find 
staff group and add user name there.
It will allow that user to read, write and execute installed programs.
When you installing anything new at /usr/local, be sure that ownership of the 
application belongs to root:staff and permission set appropriately. To do 
that, you need to execute the following commands:
to change owner ship:
a) become a root;
b) execute: chown -R root:staff 

to set permissions:
a) become a root;
b) execute: chmod -R 775 

On windows partition, these applications can be installed on C drive. When a user 
is created, be sure it has administrator permissions for the local 
machine.

When you start SmartCVS first, please set user name and password to yours in 
order to connect cvs repository on your behalf. Remember, these must be your user name and password to network.
In order to do it:
a) start smartCVS;
b) cancel to open any repository;
c) go to Projects menu and select Repository Profiles;
d) select the existing repository and click on Edit button;
e) check “Use this profile name” radio button and change default username to 
yours one;
f) enter your password;
g) click ok;

On this page I put some configuration tips for article: -Why do we need Linux in our software test lab, and how do we start using it. It can be useful software testers This ideas are very simple to implement but can be very useful for software testers.
END Configuration tips article: Why do we need Linux in our software testing lab, and how do we start using it.