First of all,share some tools for test:JUnit(nearly be the standar of java Unit test),EasyMock(a framwork that help you generate Mock object to do unit test in Mock object approach.Of course,you can use stub approach,more info please read JUnit books),cactus(which help you do in-container intergration Unite test),DBUnit(from the name,wo can know it's purpose),StrutsTestCase(used to test struts Action).
I'm also a greenhorn in test field.But i found test is not that kind of baldness as i thought before.Of course,all tests i mentioned were white-box test.So i will not share and i can't share any experince of Uni Test.But i wanna present some issues in my porject.
Now,we're in a Test phase.From the schedule,the phase name is Unit Test.But do we really do Unit Test?ok,what is unit test?In computer programming, a unit test is a method of testing the correctness of a particular module of source code.A test case is a set of  particular codes programmer writes to  test the special method. But now,all we do are even not white-box test.It's already beyond intergration test,it's function test.That can be done by tester.Test case are written on the specification.Testers follow the guide,use the system in stated way and check the expected result....I should say:we shouldn't call that unit test.So i write my unit test case of DB manipulation CLASS.Because of time is not unstinted,so i can't do unit test on Struts Action.And i will refactory my unit test case using DBUnit framework.
Maybe when i finished my documents, i will write how to use StrutsTestCase and DBUnit to do unit test.

OMG,sam told me that lishu got another project of MMC.But guess what?a VB project....FT.I suffered form these meaningless projects.What make me still be here are:tt,lishu's personality and 2w RMB  training fee.
The holy bible arrived.I hopes i can be cool to accept the fact.LOAD GOD bless me...

*********************
you've got me feeling emotions
deeper than i've ever dreamed of
you've got me feeling emotions
higher than the heavens above
i feel good
i feel nice
i've never felt so
satisfied
i'm in love
i'm alive
intoxicated
flying high
it feel like a dream
when you touch me tenderly
i don't know if it's real
but i like the way i feel
inside
you've got me feeling emotions
deeper than i've ever dreamed of
you've got me feeling emotions
higher than the heavens above
in the morning
when i rise
you are the first thing
on my mind
and in the middle
of the night
i feel your heartbeat
next to mine
it feels like a dream
when you love me tenderly
i don't know if you're for real
but i like the way i feel
inside

you've got me feeling emotions
deeper than i've ever dreamed of
you've got m

输出结果：
---------- Run ----------
s1 s2 equal
strArray equal
strArray2 equal

Output completed (1 sec consumed) - Normal Termination
首先，各位应该明白最基础的东西 ==实现的比较是浅比较，就是非reference指向的具体对象内容，而是是否指向了同一个对象。第二，String类型被设计为非可变类，就是说 String s1 = "hi";与String s2 = "hi";其实指向了同一个对象，只有用new构造函数的时候才会产生新的对象，而不管内容是否已经在内存中存在。如下文字阐述了一些：
s = new String("Initial Value");
每次都会调用构造器，生成新对象，性能低下且内存开销大，并且没有意义，因为String对象不可改变，所以对于内容相同的字符串，只要一个String对象来表示就可以了。也就说，多次调用上面的构造器创建多个对象，他们的String类型属性s都指向同一个对象。
上面的结论还基于这样一个事实：对于字符串常量，如果内容相同，Java认为它们代表同一个String对象。而用关键字new调用构造器，总是会创建一个新的对象，无论内容是否相同
ok，回到我们的话题上来String[] s2 = {"hi","hi","hi","hi","hi"};是否产生了5个不同的对象呢？我写的简单的测试代码

String[] strArray2 = {"hello","hello"};
 if(strArray2[0]==strArray2[1]) System.out.println("strArray2 equal");
的结果大家应该得出了结论了吧。
那么，bruce给出的代码的结果之所以为true就是因为，这么多个数组中的成员"hi"其实都是同一个对象。那么我们继续看Arrays.equals是否比较的内容呢？
SRC：
public static boolean equals(Object[] a, Object[] a2) {
        if (a==a2)
            return true;   //如果指向同一对象，当然是相同的，返回true
        if (a==null || a2==null)
            return false;  //如果为null就没有相等的一说，false

        int length = a.length;
        if (a2.length != length)  //长度不同
            return false;

        for (int i=0; i<length; i++) {
            Object o1 = a[i];
            Object o2 = a2[i];
            if (!(o1==null ? o2==null : o1.equals(o2)))  //此处为关键，object的equals比较，Arrays.equals并没有专门为String类型重载此方法，全部都依赖Object的方法比较
                return false;
        }

        return true;
    }

那么我们再看看Object这个树根的equals方法吧：
public boolean equals(Object obj) {
 return (this == obj);
    }

短短几行代码，但是，是浅比较毫无疑问，所以，bruce说的，依赖的是Object.equals，比较的是内容，更是错误的。
但是必须强调的是，当String数组传递进来的时候，由于java的RTTI执行期型别辨识，Arryas.equals调用的其实是String.equals方法，而String.equals方法是比较内容的，所以，此处我想是bruce没有说明白，而又偏偏列举了String的例子。如果是自己写的类有没有复写equals方法，此时就调用Object.equals了，那么根本不可能比较内容，所以Arrays.equals大家一定要知道怎么回事再用。