| || |
Java App testing
I am new to Java app testing, Previously I have done manual testing on VB,ASP .Please let me know what i should know for this testing.
Thanks in advance
Re: Java App testing
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by sreeya:
I am new to Java app testing, Previously I have done manual testing on VB,ASP .Please let me know what i should know for this testing.<HR></BLOCKQUOTE>
It all depends on the type of testing you are doing and how familiar you were with testing regarding the other languages you worked with. Testing an application written in Java is largely no different than testing an application written in Visual Basic. Both have functional aspects you can test. Both can be tested for performance issues. (Java is often a big concern for speed-related issues because of the non-native nature of the code and the fact that you are running through a glorified interpreter - the virtual machine.)
If you are talking about code-level testing (often described as "unit testing"), there are specific Java-related issues that you can check for that would differ, at least somewhat, relative to a language like Visual Basic, but it does not sound like this is something you will be dealing with. Correct me if I am wrong on that, however.
My overall point is that the same test techniques you used to test Visual Basic applications, in terms of your manual testing, can certainly be applied to testing Java applications. One concern with Java applications is often the version of the virtual machine that is being used and the operating system it is being used on. Visual Basic uses the common Windows controls (the various OCXs and DLLs) and, as such, it is much less subject to variation because each operating system comes with a standard set of the controls and a common API that the application can call. Java, by contrast, relies on the operation of the virtual machine that the user has installed on a given operating system. For users who are simpy using a Java application (as opposed to writing one) this solely consists of the Java run-time engine that is present on the machine. There is also the notion of looking into whether your Java application is utilizing any native operations on the host computer. In other words, is the Java application using one of the various means of hooking into the native code of the operating system in order to provide more functionality? Again, this is often not as much a concern with applications written in Visual Basic because Visual Basic does not have the inherent security restrictions that something like Java has.
There are a lot of things to consider, of course. For example, if your Java application connects to a remote server at all, you have to consider that as well. So there are particular issues that you want to be concerned with but the overall point is that the same test techniques you found useful testing Visual Basic and Active Server Pages manually will serve you well in testing Java applications. There is more that could be said but without knowing more about the application you are looking at or the testing you have to be concerned with, I would probably just be rambling.