Thursday, January 23, 2014

CLASSPATH settings in JAVA

PATH and CLASSPATH
This section explains how to use the PATH and CLASSPATH environment variables on Microsoft Windows, Solaris, and Linux. Consult the installation instructions included with your installation of the Java Development Kit (JDK) software bundle for current information.
After installing the software, the JDK directory will have the structure shown below.

The bin directory contains both the compiler and the launcher.
Update the PATH Environment Variable (Microsoft Windows)
You can run Java applications just fine without setting the PATH environment variable. Or, you can optionally set it as a convenience.
Set the PATH environment variable if you want to be able to conveniently run the executables (javac.exe, java.exe, javadoc.exe, and so on) from any directory without having to type the full path of the command. If you do not set the PATH variable, you need to specify the full path to the executable every time you run it, such as:
C:\Java\jdk1.7.0\bin\javac MyClass.java
The PATH environment variable is a series of directories separated by semicolons (;). Microsoft Windows looks for programs in the PATH directories in order, from left to right. You should have only one bin directory for the JDK in the path at a time (those following the first are ignored), so if one is already present, you can update that particular entry.
The following is an example of a PATH environment variable:
C:\Java\jdk1.7.0\bin;C:\Windows\System32\;C:\Windows\;C:\Windows\System32\Wbem
It is useful to set the PATH environment variable permanently so it will persist after rebooting. To make a permanent change to the PATH variable, use the System icon in the Control Panel. The precise procedure varies depending on the version of Windows:
Windows XP
1.     Select Start, select Control Panel. double click System, and select the Advanced tab.
2.     Click Environment Variables. In the section System Variables, find the PATH environment variable and select it. Click Edit. If the PATH environment variable does not exist, click New.
3.     In the Edit System Variable (or New System Variable) window, specify the value of the PATH environment variable. Click OK. Close all remaining windows by clicking OK.
Windows Vista:
1.     From the desktop, right click the My Computer icon.
2.     Choose Properties from the context menu.
3.     Click the Advanced tab (Advanced system settings link in Vista).
4.     Click Environment Variables. In the section System Variables, find the PATH environment variable and select it. Click Edit. If the PATH environment variable does not exist, click New.
5.     In the Edit System Variable (or New System Variable) window, specify the value of the PATH environment variable. Click OK. Close all remaining windows by clicking OK.
Windows 7:
1.     From the desktop, right click the Computer icon.
2.     Choose Properties from the context menu.
3.     Click the Advanced system settings link.
4.     Click Environment Variables. In the section System Variables, find the PATH environment variable and select it. Click Edit. If the PATH environment variable does not exist, click New.
5.     In the Edit System Variable (or New System Variable) window, specify the value of the PATH environment variable. Click OK. Close all remaining windows by clicking OK.

Note: You may see a PATH environment variable similar to the following when editing it from the Control Panel:
%JAVA_HOME%\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem
Variables enclosed in percentage signs (%) are existing environment variables. If one of these variables is listed in the Environment Variables window from the Control Panel (such as JAVA_HOME), then you can edit its value. If it does not appear, then it is a special environment variable that the operating system has defined. For example, SystemRoot is the location of the Microsoft Windows system folder. To obtain the value of a environment variable, enter the following at a command prompt. (This example obtains the value of the SystemRoot environment variable):

echo %SystemRoot%


-- 

Open Command Prompt . type following line

Set path=%path%+;C:\Program Files\Java\jdk1.6.0_23\bin

check ,  c:\>javac


Manual Testing


Black Box Testing & Design Techniques



Black box testing tests the functionality of the application without having the knowledge of internal structure of the code. Black box testing is also called as Specification based testing. This testing can be applied in all levels of testing namely system, integration, acceptance testing.

Black box testing design techniques are
  • Decision table testing
  • All pairs testing
  • State transition tables
  • Equivalence partitioning
  • Boundary value analysis


Decision Table testing

We have an application which works based on simple true/false condition of a variable. So in decision based testing we will test for both the conditions. What happens when the variable status is true or what happens if it is false?  This is mostly like if-then-else, switch cases with each condition having some actions to perform.  So we need to test all the actions.

All pairs testing

Consider an application where we need to supply value to some three input parameters. So we need to test all possible combinations of input based on probability.  We have to consider all possible scenarios like,
  •  If we give value for all 3 parameters
  • If we do not give value for all 3 parameters
  • If we give value for 2 parameters.

Likewise we need to test. This testing is mainly to produce optimal number of test cases.  We do not want to perform the entire test based on the probability (3 * 2) since we have 3 parameters but we can achieve the result by some combinations of input.

State transition tables

This table shows the current state of the machine and to which status the machine will move to based on input parameters. Consider an application where the state of the machine will move from s1 to s2 if the parameter is 1. If it is zero it will be in same state. We can represent the same as,


State
Input  ‘0’
Input  ‘1’
S1
S1
S2
S2
S2
S1

Equivalence partitioning

This involves partitioning the data in to some best partitions so that one test case is enough to cover each partition.  Consider an application where the app will work only if the value supplied by the user is between 10 to 15. So we can divide these as
  • 1 to 10 as one partition
  • 10 to 15 as second
  • > 15 as third.

So while testing any one value from each partition is enough to test. After portioning we have to apply boundary value cases in order to select the best suited test case from each partition.

Boundary value analysis

Here we have to consider the boundary values for testing. Consider a refrigerator application where it should defrost when the temperature is below 0 degrees and it should start cooling when the temperature is above 10 degrees.

So the boundary conditions will be
  •          below  0 degrees (- 1, -2, …)
  •          Above 10 degrees (11, 12...)
  •          At  0 degree
  •          At 10 degree


By these black box testing design techniques we can test the application with optimal number of test cases and the test cases selected are of most suited so that we can reduce the defect slippage.