Server Side Unit Tests / arquillian

Hello,
has anyone successfully used arquillian to perform server side unit tests with NetWeaver AS? Or any other way to achieve this goal (test EJBs in their native environment)?
A while ago we achieved this by manually deploying and running the tests on the server, but this is not a clean solution like arquillian, and required some workaround and design restrictions on the application.
ciao,
Elmar

Not presently, we have the same issue internally. I have a half-finished "Headless Glass" implementation would allow exactly this, but due to other (crucial and exciting) FX work I am doing at the moment, I haven't been able to finish this.

Similar Messages

  • "RABAX" occurs on server side error while testing asynchoronous web service

    I got error while testing asynchronous web service in WS navigator. I have created asynchronouse web service using RFC. Then I configured it in SOAMANAGER. When I tested it, got error "RABAX occurs on server side". Also I got dump in ST22. It is 'UNCHAUGHT_EXCEPTION - CX_SOAP_SEQ_SCD_ERROR'.
    I have tested for synchronous web service it works fine.  I found a difference in both web service WSDL file for below parameters value -
    commit
    blocking
    transaction
    wsrm
    I tried different way .. but no solution .. Plz suggest if someone have any idea.....Its very helpfull....

    your problem:
    Missing class: oracle.tip.adapter.jms.JmsManagedConnectionFactory
    Dependent class: oracle.tip.adapter.fw.wsdl.WSDLUtils
    Loader: oracle.bpel.common:10.1.3
    Code-Source: /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar
    Configuration: <code-source> in /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml
    It happens when server is custom installed, try to reinstall it as full version and problem should disappear otherwise your need another full installation to retrieve and replace orabpel.jar file from (or maybe more)

  • SSDT: Creation of localDB instances from project file - Sql Server Unit testing purposes

    I have a SqlServer Database Project in my solution (VS2013 Professional) which has a corresponding test project with some stored procedure unit tests. Currently I am using a LocalDB and as far as I understand a local database instance is created in C:\Users\[User]\AppData\Local\Microsoft\Microsoft
    SQL Server Local DB\Instances\Projects and the specific .mdf file referenced in the SQL Server Object Explorer is in C:\Users\[User]\AppData\Local\Microsoft\VisualStudio\SSDT\[ProjectName]. The unit tests run fine on my local machine which I have developed
    the project on.
    My issue is we have a box which is configured to check out the project file from our version control, build the project using ms build commands and then run the unit tests using VSTest.Console. Usually with C# Test projects we reference the test project
    dll and the unit tests run fine. I have referenced the dll for the test project with the stored procedure unit tests in. 
    With the Stored Procedure unit tests however we get this exception: 
    Initialization method [project].[spTest].TestInitialize threw exception. System.Data.SqlClient.SqlException: System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 50 - Local Database Runtime error occurred. The specified LocalDB instance does not exist.
    After some digging I have realised that the localdb instance seems to be created when the project itself is created in VS not when it is built. Specifically when the localdb is first used and if you look into the appData folder of the test machine there
    is no corresponding mdf file for the project.  
    The question is is there a way to set up a localDB instance on the new machine if all you have the project file? The only purpose of the project on the test machine is to run the unit tests, no other development purposes. VS2013 Professional is installed
    on the test machine but a solution only using config file changes or MSBuild/VSTest commands would be preferable.
    I realise you could change the connection string to an actual test database and run the unit tests of that but we quite like the localdb approach for the testing. I also realise that you could potentially transfer the mdf file (haven't tested this solution)
    as well, though I would prefer if there is a solution to my initial question. 
    http://technet.microsoft.com/en-us/library/hh234692.aspx
    http://msdn.microsoft.com/en-us/library/hh309441(v=vs.110).aspx
    I have been reading up on LocalDB and I assume a automatic LocalDB is created when you create a sql server database project (ie on localdb first use). I have tried adding the database creation to the test project config file but do not really know where
    to go from there. The second link does not really specify when the named localdb will be created if you add the config items and I am not even sure if that is an actual solution.  Here's my test project config file for reference
    <configSections>
    <section name="system.data.localdb" type="System.Data.LocalDBConfigurationSection,System.Data,Version=4.0.0.0,Culture=neutral,PublicKeyToken=[PublicKeyToken]"/>
    <section name="SqlUnitTesting_VS2013" type="Microsoft.Data.Tools.Schema.Sql.UnitTesting.Configuration.SqlUnitTestingSection, Microsoft.Data.Tools.Schema.Sql.UnitTesting, Version=12.0.0.0, Culture=neutral, PublicKeyToken=[PublicKeyToken]" />
    </configSections>
    <system.data.localdb>
    <localdbinstances>
    <add name="SimpleUnitTestingDB" version="11.0" />
    </localdbinstances>
    </system.data.localdb>
    <SqlUnitTesting_VS2013>
    <DatabaseDeployment DatabaseProjectFileName="..\..\..\SimpleUnitTestDB\SimpleUnitTestDB.sqlproj"
    Configuration="Release" />
    <DataGeneration ClearDatabase="true" />
    <ExecutionContext Provider="System.Data.SqlClient" ConnectionString="Data Source=(localdb)\Projects;Initial Catalog=SimpleUnitTestDB;Integrated Security=True;Pooling=False;Connect Timeout=30"
    CommandTimeout="30" />
    <PrivilegedContext Provider="System.Data.SqlClient" ConnectionString="Data Source=(localdb)\Projects;Initial Catalog=SimpleUnitTestDB;Integrated Security=True;Pooling=False;Connect Timeout=30"
    CommandTimeout="30" />
    </SqlUnitTesting_VS2013>
    Thanks in advance for any response. Sorry if there is any misunderstanding, while I have been using VS to develop from the start, this is the first time I have used a Sql Server Database Project. 
    Regards,
    Christopher. 

    Yes, you can create a LocalDB instance manually. You use the SqlLocalDb utility, see here:
    http://technet.microsoft.com/en-us/library/hh212961.aspx
    Erland Sommarskog, SQL Server MVP, [email protected]

  • Trouble Testing Server Side Includes using personal web sharing

    I am using the book "Standard complant websites using dreamweaver 8" One of the exercises has me testing that server side includes are enabled by creating two files ssi_test.shtml and hello.html. I have placed these two files in the documents subfolder which web server is the main folder.
    Since I only see a blank page when I test, the book says I need to tweak the Apache configuration to enable SSI. It says to open httpd.conf file (which I can not find) . I am suppose to insert the following lines: AddType text/html .shtml and Addhandler server-parsed .shtml
    Where is this file httpd.conf file located?
    How do I modify it?
    Thanks for your support
    James
    powermac G4 Mac OS X (10.3.9)

    It is in /private/etc/httpd directory.
    You will need a file editor that knows how to authenticate or to learn some basics with the command line and unix to use sudo to edit the file.
    <pre>sudo pico /private/etc/httpd/httpd.conf</pre> is where I recommend you start if you don't know emacs or vi or another of the fine unix editing tools that are provided...
    An article that was intended to fix a different problem - but has all the steps you need to locate the terminal application, learn about sudo, etc... is http://docs.info.apple.com/article.html?artnum=301580

  • Using SQLCMD variables in SQL Server Unit Test Project

    Is it possible to use SQLCMD variables in my SQL Server Unit Test Project? In my test initialize script I'd like to set a database name variable, something like this:
    :SETVAR MyDatabase "mydatabase"
    SELECT * FROM [$(MyDatabase)].[mytable]
    but I get syntax errors when I run the test. Any suggestions how I can get this to work.
    Result Message: Initialization method
    myTest.TestInitialize threw exception. System.Data.SqlClient.SqlException: System.Data.SqlClient.SqlException:
    Incorrect syntax near ':'..

    Hi Kevin,
    What is the error?
    This should work only thing i could see is no scheme specified.
    SQL Server uses dbo as default schema.
    In your case:
    :SETVAR MyDatabase "mydatabase"
    SELECT * FROM [$(MyDatabase)].dbo.[mytable]
    Also check your instance collation if its Case sensitive then specify database and table name as exact case.
    Example:
    :SETVAR MyDatabase "[mydatabase]"
    :setvar schemavar "[dbo]"
    :setvar tablevar "[mytable]"
    SELECT * FROM $(MyDatabase).$(schemavar).$(tablevar)

  • Server Side Load Balancing Testing

    Hi,
    Can any one tell me about any test case for server side load balancing in an 11.1.0.7 RAC?
    I have a 2 nodes RAC with local_listener and remote_listener set properly (for server side load balancing). For testing, i have create a TNS at my client side which points to only one node of RAC (a single ADDRESS entry pointing to node 1 of my RAC). So, from this client, when ever i connect, it always connects me to the node 1 which i have mentioned in the TNS. Does it mean that server side load balancing works in conjunction with client side load balancing only and i should add ADDRESS entry in my TNS for the second node also? If yes, then how can i create a test case to check server side load balancing?
    Thanks
    Salman

    Thanks Rajeysh but i already have seen these documents after "googling" about server side load balancing but these documents don't give my any idea for testing the server side load balancing. My goal is actually testing the following scenario
    Creating a TNS entry to connect to a RAC database (with server side load balancing enabled) by using a single ADDRESS line in TNS which points to node1 to connect to service on node 1 (service_name is set to same value on all the nodes).
    Now, if i invoke 10 SQLPLUS windows to connect to the RAC database using this TNS, it always connects me to instance 1 running on node 1, where is server side load automatic load balancing? Why new sessions are not being directed to some other instance and why every time i always connect to instance 1?
    Salman

  • SQL Server Unit Tests

    Hi SQL Server Experts,
    About SQL Server Unit Tests (vide
    http://msdn.microsoft.com/en-us/library/jj851203(v=vs.103).aspx), please help with inputs on pros and cons of SQL Server Unit Tests. Any ideal recommendation?
    Thanks

    Blog on the topic: "Database unit testing is used for feature testing of your individual modules (stored procedures, triggers or user defined functions) that is to say your module performs as expected.  Apart from that, it is also used to ensure that
    subsequent changes to the module does not break any functionality.
    At first glace, it looks like this would add overhead to create vs. doing adhoc testing, but Visual Studio lets you automatically generate T-SQL code stubs to test the database object which you can customize as per your need.
    Visual Studio provides Database Unit Test Designer which you can write/define T-SQL scripts (also insert SQL assertion in this code) that calls your module and then evaluates the execution result against the different test conditions which indicates your
    modules execution success or failure."
    LINK:
    SQL Server Unit Testing with Visual Studio 2010
    >Please pardon my ignorance as I am coming back to SQL Server after a brief gap.
    You may have to brush up with T-SQL prior to using a sophisticated tool like this:
    http://www.sqlusa.com/bestpractices/
    Kalman Toth Database & OLAP Architect
    SQL Server 2014 Design & Programming
    New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

  • [svn:osmf:] 11045: Increasing timer interval in attempt to fix unit test on the build server.

    Revision: 11045
    Author:   [email protected]
    Date:     2009-10-21 02:32:45 -0700 (Wed, 21 Oct 2009)
    Log Message:
    Increasing timer interval in attempt to fix unit test on the build server.
    Modified Paths:
        osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/composition/TestParallelViewableTrai t.as

    In general theory, one now has the Edit button for their posts, until someone/anyone Replies to it. I've had Edit available for weeks, as opposed to the old forum's ~ 30 mins.
    That, however, is in theory. I've posted, and immediately seen something that needed editing, only to find NO Replies, yet the Edit button is no longer available, only seconds later. Still, in that same thread, I'd have the Edit button from older posts, to which there had also been no Replies even after several days/weeks. Found one that had to be over a month old, and Edit was still there.
    Do not know the why/how of this behavior. At first, I thought that maybe there WAS a Reply, that "ate" my Edit button, but had not Refreshed on my screen. Refresh still showed no Replies, just no Edit either. In those cases, I just Reply and mention the [Edit].
    Also, it seems that the buttons get very scrambled at times, and Refresh does not always clear that up. I end up clicking where I "think" the right button should be and hope for the best. Seems that when the buttons do bunch up they can appear at random around the page, often three atop one another, and maybe one way the heck out in left-field.
    While I'm on a role, it would be nice to be able to switch between Flattened and Threaded Views on the fly. Each has a use, and having to go to Options and then come back down to the thread is a very slow process. Jive is probably incapable of this, but I can dream.
    Hunt

  • [svn] 3718: Make sure the server is stopped even when a unit test fails.

    Revision: 3718
    Author: [email protected]
    Date: 2008-10-17 13:03:17 -0700 (Fri, 17 Oct 2008)
    Log Message:
    Make sure the server is stopped even when a unit test fails. Thanks to Alex for the fix.
    Modified Paths:
    blazeds/trunk/modules/core/build.xml

    I had the same issue after upgrading from 10.7.2 to 10.7.3 and changing my main SSL cert.
    The solution was to make sure the correct cert was listed in:
    /etc/openldap/slapd.conf
    as well as:
    /etc/openldap/slapd.d/cn=config.ldif
    It looks as though the slapd.conf file gets updated properly when you select an SSL cert in the Server Admin app, but the cn=config.ldif does not. That is the one that was hanging my server up.
    Hope this helps!

  • How to debug in dedicated unit test client

    Hello,
    We have a setup where we do all development in client 100, but have a separate client for unit tests. Since this is the client holding relevant test data, we would like to debug in this client.
    How can I achieve this in Eclipse, do I need to create two projects (one for each client) and open the object twice, or is it possible to setup using debug configurations or something similar?
    Regards

    Hi Matthias,
    in Java you need OS privileges to debug Java code running on any Java application server (and additionally set up the Java VM in debug mode and stuff like that). And once you have OS privileges, you can of course debug all Java VM processes/threads on the machine, regardless which application context they are currently running for.
    In ABAP you do NOT need any kind of OS privileges in order to debug. All you need is a user in the system/client with debug privileges, which is big advantage in terms of privilege separation. ABAP debugging on customer systems for example, which is a quite normal thing, would be much harder to realize, if we require any kind of OS privileges.
    To cut a long story short:
    As a user is required with debugging privileges in any ABAP system/client for ABAP debugging, it is not possible to realize a remote debugging in ABAPinEclipse just by specifying SID/client of the remote ABAP system.
    So you need to logon to the ABAP system/client (and set breakpoints there) in order to debug. And as the system/client logon to the ABAP backend in ABAPinEclipse is conceptually linked to a project, you need to have an open project for those ABAP system/clients you want to debug in.
    Regards,
    Christoph Stoeck, ABAP Language

  • Server side package or emrbace Apex and use its capability

    This may not be a suitable question for this forum but I can only try.
    My experience with APEX is primarily doing everything in the APEX “front end” and only calling PL/SQL packages in the database when absolutely necessary.
    A colleague insists on putting everything in a PL/SQL package in the database and putting calls in APEX to functions & Packages.
    One example I can quote is we had a conditional tab which could only be viewed if you had an entry in a table.
    I did the SQL code for the tab in the conditions section in apex. My colleague then reworked my code to call a PL/SQL package and placed the code I had written on the server.
    Another example was a demo of lazy load on an input field he loved it but then when he realised it could not be done via a call to a server side package dismissed the lazy load idea as not relevant even though it would make our users life easier.
    I am soon to have a battle royal over which is the best approach. Any comments.

    First of all: All PL/SQL Logic you enter, either in APEX or in packages is always executed on the server. Your browser doesn't understand PL/SQL very well...
    Putting PL/SQL logic in packages - instead of in APEX regions - has some advantages though (not extensive list):
    - You can easily unit test package procedures/functions.
    - You can reuse the package procedures/functions in the same app or in other apps as well.
    - PL/SQL code in packages is compiled in APEX it's dynamic and has to be parsed, so creates some overhead.
    - When you make changes to your codebase or columns you can spot that in your PL/SQL packages (they might get invalid). You won't notice that in your APEX regions until you (or end user) run the page and encounter an error.
    So, yes, putting logic in packages has advantages. But on the other hand, a statement like "if we can't do it in a package, we don't do it all" might be a little to restrictive...
    Just my 2 cents

  • JUNIT USING AT SERVER SIDE

    Hi,
    i hava one dought
    regarding JUNIT
    it is testing client programs.
    how to test Server side programs
    plz send any information on this JUNIT testing on server side

    JUnit is doing unit tests, regardless of client or server. You seem to want to do integration tests or system tests.

  • Unit Testing

    Hi All,
    I would like to inform to all, can any one explain to me the concept of Unit testing in FICO and how it should be drawn? If possible send any dcoumentation for this focus to my mail id: [email protected]
    Thanks with regards,
    Bala

    Hi
    refer below reward if helps
    Unit testing is done in bit and pieces. Like e.g. in SD standard order cycle; we do have 1-create order, then 2-delivery, then 3-transfer order, then 4-PGI and then 5-Invoice.  So we will be testing 1,2,3,4 and 5 seperately alone one by one using test cases and test data. We will not be looking and checking/testing any integration between order and delivery; delivery and TO; TO and PGI and then invoice.
    Whrereas System testing you will be testing the full cycle with it's integration, and you will be testing using test cases which give a full cyclic test from order to invoice.
    Security testing you will be testing different roles and functionalities and will check and signoff.
    Performance testing is refered to as how much time / second will take to perform some actions, like e.g. PGI.  If BPP defination says 5 seconds for PGI then it should be 5 and not 6 second.  Usually it is done using software.
    Regression testing is reffered to a test which verfies that some new configuration doesnot adversly impact existing functionality.  This will be done on each phase of testing.
    User Acceptance Testing:  Refers to Customer testing. The UAT will be performed through the execution of predefined business scenarios, which combine various business processes. The user test model is comprised of a sub-set of system integration test cases.
    We use different software during testing. Most commonly use are
    Test Director:  which is used to record requirement, preparing test plan and then recording the progress.  We will be incorporating defects that are coming during these testings using different test cases.
    Mercury Load Runner:  is used for performance testing.  This is an automatic tool.
    What does the following terms means :
    - Technical Unit Testing
    - Functional Unit Testing
    - IntegrationTesting
    - Volume Testing
    - Parallel Testing?
    Technical Unit Testing= Test of some technical development such as a user exit, custom program, or interface. the test usually consists of a test data set that is processed according to the new program.  A successful test only proves the developed code works and that it performed the process as as designed.
    Functional Unit Testing= Test of configuration, system settings or a custom development (it may follow the technical unit testing) These usually use actual data or data that is masked but essentially the same as a real data set. A successful test shows that the development or configuration works as designed and the data is accurate as a result.
    IntegrationTesting= Testing a process, development or configuration within the context of any other functions that the process, development or functionality will touch or integrate . The test should examine all data involved across all modules and any data indirectly affected. A successful test indicates that the processes work as designed and integrate with other functions without causing any problems in any integrated areas.
    Volume Testing= testing a full data set that is either actual or masked to insure that the entire volume does cause system problems such as network transmission problems, system resources issues, or any systemic problem, A successful test indicates that the processes will not slow or crash the system due to a full data set being utilized.
    Parallel Testing= Testing the new system or processes with a complete data set while running the same processes in the legacy system. A successful test will show identical results when both the legacy system and new system results are compared.
    I would also note that when a new implementation is being done you will want to conduct at least one cut over test from the old system to the new and you should probably do several.
    What kind of testings that are carried out in testing server?
    1. Individual Testing ( Individually which we've created)
    2. Regressive Testing ( Entire Process)
    3. Integration Testing ( Along with other integrated modules)
    The 3 types of testing is as follows:-
    1. Unit testing (where an individual process relevant to a SD or MM etc is tested)
    2. Integration testing (where a process is tested that cuts across all areas of SAP).
    3. Stress testing (where lots of transactions are run to see if the system can handle the data)
    http://www50.sap.com/businessmaps/6D1236712F84462F941FDE131A66126C.htm
    Unit test issues
    The unit tools test all SAP development work that handles business object processing for the connector. Also, the unit test tools enable you to test the interaction of your work with the ABAP components of the connector. The test tools allow you to test your development work as an online user (real-time) only.
    Note:
    It is important to understand the differences between testing the connector as an online user and testing the connector as if operating as a background user.
    The differences between testing the connector as an online user or as a background user are described as follows:
    Memory--When testing a business object, the connector must log into the SAP application.
          The connector runs as a background user, so it processes in a single memory space that is never implicitly refreshed until the connector is stopped and then restarted (therefore it is critical in business object development to clear memory after processing is complete). Since you are an online user, memory is typically refreshed after each transaction you execute.
          For more information, see Developing business objects for the ABAP Extension Module. Any problems that may occur because of this (for example, return codes never being initialized) are not detected using the test tool; only testing with the connector will reveal these issues.
    Screen flow behavior--Screen flow behavior is relevant only when using the Call Transaction API. The precise screen and sequence of screens that a user interacts with is usually determined at runtime by the transaction's code. For example, if a user chooses to extend a material master record to include a sales view by checking the Sales view check box, SAP queries the user for the specific Sales Organization information by presenting an additional input field. In this way, the transaction source code at runtime determines the specific screen and its requirements based on the data input by the user. While the test tool does handle this type of test scenario, there is a related scenario that the test tool cannot handle.
          SAP's transaction code may present different screens to online users versus background users (usually for usability versus performance). The test tool only operates as an online user. The connector only operates as a background user. Despite this difference, unit testing should get through most of the testing situations.

  • Unit testing in J2EE environment

    Hi All:
    We have been trying to use Junit for creating unit test scripts, and have been bit successful in unit testing DAOs and Value objects - but problem is testing of components like EJBs and Servlets or even classes like Actions or Commands. Since these components run under application server environment, I am not sure how to unit test them without either deploying them on the actual server or simulating app server and rest of the system.
    I was wondering if people could share their experience in writing unit test scripts especially for J2EE components - like Servlets, JSPs and EJBs. On the similar note, is there any similar tool or API for creating integration test scripts?
    Thanks,

    Well - we already have couple of other servers but that's for beta, QA and Integration testing. Problem is with the unit testing. In unit testing, some piece of code is tested by itself. And I am not sure how I can unit test some of the classes like Servlets, EJBs, JSPs or even dependent classes like Commands or Actions. For example, consider following Action class from Java Pet Store:
    public final class CartHTMLAction extends HTMLActionSupport {
    public Event perform(HttpServletRequest request)
    throws HTMLActionException {
    // Extract attributes we will need
    String actionType= (String)request.getParameter("action");
    HttpSession session = request.getSession();
    // get the shopping cart helper
    CartEvent event = null;
    if (actionType == null) return null;
    if (actionType.equals("purchase")) {
    String itemId = request.getParameter("itemId");
    event = new CartEvent(CartEvent.ADD_ITEM, itemId);
    else if (actionType.equals("remove")) {
    String itemId = request.getParameter("itemId");
    event = new CartEvent(CartEvent.DELETE_ITEM, itemId);
    else if (actionType.equals("update")) {
    Map quantities = new HashMap();
    Map parameters = request.getParameterMap();
    for (Iterator it = parameters.keySet().iterator();
    it.hasNext(); ) {
    String name = (String) it.next();
    String value = ((String[]) parameters.get(name))[0];
    final String ITEM_QTY = "itemQuantity_";
    if (name.startsWith(ITEM_QTY)) {
    String itemID = name.substring(ITEM_QTY.length());
    Integer quantity = null;
    try {
    quantity = new Integer(value);
    catch (NumberFormatException nfe) {
    quantity = new Integer(0);
    quantities.put(itemID, quantity);
    event = CartEvent.createUpdateItemEvent(quantities);
    return event;
    In order to unit test above class from say, JUnit test script class, I will have to pass HttpServletRequest object to its method - I will also have to store corresponding command params and store them in the request object - how will you write unit test script for the above class?

  • Unit testing in nitrox

    I am new to eclipse and nitrox. Have been building webapps for years with IDEA.
    1) I find info in eclipse help concerning Junit based testing, I find nothing about unit testing in NitroX help. The webapps I am trying to import and build in NitroX must support unit testing. Eclipse Junit based help does not work for me in NitroX webapp.
    2) I have created several types of new webapps in NitroX accepting default parameters in wizard hoping to see how NitroX would lay out a new development environment. None of the results comes close to the development structure described in eclipse help. I find a src folder inside WEB-INF folder. This does not make sense to me and I can find no explanation of what NitroX expects with regards to project structure other than the existence of WEB-INF just below webapp context folder. My ultmate goal is to use both NitorX and IDEA accessing the same CVS repositories. So far I have imported several existing webapps via 'folder import' of source tree, but NitroX does note 'see' my testsrc or testbuild branches and I can not run tests except via my own custom Ant scripts. Any suggetions?
    Thanks

    1) I find info in eclipse help concerning Junit based testing, I find nothing about unit testing in NitroX help. The webapps I am trying to import and build in NitroX must support unit testing. Eclipse Junit based help does not work for me in NitroX webapp.
    If you have a Java class that extends JUnit, then in Eclipse, when you're in the Java-perspective, you can right-click on that class, "Run As..." and select "JUnit Test." That'll give you the JUnit Green or Red bar based on whether the tests succeeded/failed, etc.
    NitroX = Eclipse + Struts functionality. Anything you could do in Eclipse, you can do using NitroX.
    You could, for example, switch to the Java-perspective and perform JUnit testing exactly as in Eclipse without NitroX. Or, if you're in NitroX's "Web" perspective, you can go into Package Explorer and run JUnit tests from there.
    Re: 2)
    NitroX puts a "src" folder in your WEB-INF and sets that to be a source code folder, probably so when the application is deployed on the server, the source code is also on that server (in the isolated-from-the-web WEB-INF directory), which can be beneficial for several reasons, including your development environment and CVS server crashing.
    You could delete that folder, though, and use a folder you created yourself as a source code folder for that project. You'd just have to make sure that when you designate that source code folder (via: right-click on the project -> Properties -> Java Build Path -> Source Folders), you designate the output target of that folder to be /WEB-INF/classes. That'll make sure that, regardless of where your .java files are, your .class files will be placed in the appropriate folder inside your web application structure.
    Regarding NitroX not "see"ing your testsrc or testbuild branches (I assume you mean "folders" instead of "branches" ...), I'm assuming you're using NitroX's "Web" perspective, and looking for those folders in the AppXplorer window. Since your JUnit tests are not a part of the Struts application, you won't find them there -- instead, click over to the Package Explorer view, or switch over to Eclipse's Java Perspective, where everything will behave exactly as you'd expect.
    I hope this helps ..

Maybe you are looking for