December 2007 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: New test structure

by timfox

"jmesnil" wrote : | There is also the alternative to put the different types of test related to a single "component" under the same tree. | | e.g. for remoting; all tests related to remoting would be under org.jboss.messaging.test.remoting: | - org.jboss.messaging.test.remoting.unit | - org.jboss.messaging.test.remoting.integration | - org.jboss.messaging.test.remoting.timing | - ... | | | So, "remoting" in your above example should be "core.remoting" surely? So we mirror the exact package names? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111623#4111623 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111623

18 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: New test structure

by jmesnil

"timfox" wrote : Following on from the new JBM 2.0 test strategy, we need to come to concensus on a package structure for the tests, since currently we're all putting them in different places. | | I suggest: | | org.jboss.test. parent directory - all tests are under this | Shouldn't we put our code under org.jboss.messaging.test to avoid (very unlikely) name collision with other JBoss projects? "timefox" wrote : | e.g. org.jboss.test.unit.messaging.core.impl would contain unit tests for the core implementation classes | | Comments/suggestions? There is also the alternative to put the different types of test related to a single "component" under the same tree. e.g. for remoting; all tests related to remoting would be under org.jboss.messaging.test.remoting: - org.jboss.messaging.test.remoting.unit - org.jboss.messaging.test.remoting.integration - org.jboss.messaging.test.remoting.timing - ... This mimics the way the code is hierarchized (all remoting code is under org.jboss.messaging.remoting and its subpackages) and the tests related to a same component/"theme are closer to each other than spread all over the test suite. imho, it makes it easier to navigate the code and run tests from an IDE And this won't change the way the tests are run automatically (org.jboss.messaging.test.**.unit instead of org.jboss.messaging.test.unit.**) What do you think? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111613#4111613 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111613

18 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Refactoring ServerPeer

by timfox

I've added you as a committer. Could you actually hold off committing for a little while? - we may have to do a customer patch from this branch. Will know in a few hours... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111604#4111604 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111604

18 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - EasyMock

by timfox

BTW I started using EasyMock for mocking in unit tests - it's pretty cool and takes a lot of the drudgery out of writing mocks and testing whether methods on the mocks have/haven't been called in the correct order. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111602#4111602 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111602

18 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - New test structure

by timfox

Following on from the new JBM 2.0 test strategy, we need to come to concensus on a package structure for the tests, since currently we're all putting them in different places. I suggest: org.jboss.test. parent directory - all tests are under this org.jboss.test.unit unit tests - only use mocks and fakes of 3rd party components - fully deterministic org.jboss.test.unit.fakes any shared fake implementations that can be used by different tests org.jboss.test.integration integration tests - use real third party components - fully deterministic org.jboss.test.timing timing sensitive tests - e.g. scheduled delivery tests - allowed to contain Thread.sleeps(), theorertically may be non deterministic due to timing differences in thread scheduling. org.jboss.test.concurrent - concurrent tests - like unit tests but may use multiple threads to test a component with concurrently. org.jboss.test.stress - stress tests under each of the preceeding directories the actual tests would be structured according to the classname. e.g. org.jboss.test.unit.messaging.core.impl would contain unit tests for the core implementation classes Comments/suggestions? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111601#4111601 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111601

18 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBM 2.0 JDBCPersistenceManager - volunteers?

by timfox

Can you give examples/ pointers on how you would use Hibernate to just get the DB specific SQL? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111588#4111588 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111588

18 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBM 2.0 JDBCPersistenceManager - volunteers?

by timfox

Well the main motivation for using HIbernate is to avoid us having to keep different DDL and DML configs for different databases. If we can use Hibernate to provide the DML and DDL, and forget the ORM stuff (which we don't need anyway) then that's great. But I know very little about Hibernate and what it is capable of, so don't know if that is possible. I should probably get up to speed with Hibernate... :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111587#4111587 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111587

18 years, 4 months

1
0
0 / 0

[Design of POJO Server] - Re: Porting Hibernate MBean / deployer

by alesj

Looks like HSQL problem with closed session prior to getting the id: - http://hudson.qa.jboss.com/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15/228/... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111571#4111571 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111571

18 years, 4 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: HOWTO: remove a deployment context that is in error?

by dimitris＠jboss.org

So getting back to the JIRA that started this thread: http://jira.jboss.com/jira/browse/JBAS-4292 It seems there is nothing to do there, other than fixing the testsuite to properly undeploy stuff when things go wrong, correct? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111568#4111568 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111568

18 years, 4 months

1
0
0 / 0

[Design of JBoss/Tomcat Integration] - WebAppClassLoader getURLs() override

by dimitris＠jboss.org

Related to this JIRA opened by Adrian, currently unassigned: http://jira.jboss.com/jira/browse/JBAS-5022 Is this just a matter of adding returning an empty array from getURLs()? Is this related to the discussion about the iiop stub generation in this forum thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=124610 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111566#4111566 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111566

18 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums December 2007