java.net: Wiki

The Source for Java Technology Collaboration


 <<O>>  Difference Topic MobicentsQA (15 - 17 Jan 2006 - Main.ivelin)
Line: 1 to 1
 
META TOPICPARENT name="MobicentsOpenSLEE"

Mobicents Quality Assurance

Line: 38 to 38
 Results from each continuous build are sent to a designated mailing list, which is regularly archived.
Added:
>
>

How To Run the TCK

See the instructions here: MobicentsQuickStartGuide#Run_the_TCK

 

Performance Testing and Benchmarking


 <<O>>  Difference Topic MobicentsQA (14 - 09 Jan 2006 - Main.ivelin)
Line: 1 to 1
 
META TOPICPARENT name="MobicentsOpenSLEE"

Mobicents Quality Assurance

Line: 43 to 43
 

Added:
>
>

Test bed for JSLEE 1.1 features

There is a test bed dedicated to tests that cover new features developed against JSLEE 1.1. The home directory is /thirdparty/jain-slee-1.1-tck.

 -- Main.ivelin - 08 May 2005


 <<O>>  Difference Topic MobicentsQA (13 - 24 Dec 2005 - Main.ivelin)
Line: 1 to 1
 
META TOPICPARENT name="MobicentsOpenSLEE"

Mobicents Quality Assurance

Changed:
<
<
Thanks to Emil Ivov, The Mobicents project has coninuously running build and test systems.
>
>
The Mobicents project has coninuously running build and test systems to ensure its robustness and standards compliance.
 

Continuous Builds

Changed:
<
<
After each CVS check-in, the build system automatically rebuilds the full source tree to ensure source code integrity. The reports can be found at: http://proxenet.u-strasbg.fr:8080/cruisecontrol/buildresults/mobicents
>
>
After each CVS check-in, the build system automatically rebuilds the full source tree to ensure source code integrity. The latest reports can be found on the designated mailing list: https://mobicents.dev.java.net/servlets/SummarizeList?listName=cruisecontrol&by=date
 
Changed:
<
<

Nightly run of SLEE TCK (Technology Compatibility Kit)

>
>

Nightly runs of SLEE TCK (Technology Compatibility Kit)

 
Changed:
<
<
Once a day the latest source tree (CVS HEAD) is automatically checked out and tested against the TCK.

The results for Linux are published at:

>
>
To ensure full compliance with JSLEE on continuous basis, each day the latest source tree (CVS HEAD) is automatically checked out and tested against the TCK. This procedure is executed on multiple platforms:
 
Added:
>
>
  • Solaris 9, JDK 1.4.2 running on carrier grade Sun Netra 440; maintained by Aepona
    • Results are posted on the mailing list. Note that the TCK results are attachments to the messages.
  • Linux, JDK 5.0; maintained by Emil Ivov, Lois Pasteur University
 
Changed:
<
<
The results for Solaris 9, JDK 1.4.2 can be found on the designated mailing list. They are executed on Sun Netra 440, which is a popular carrier grade server:
>
>
If you would like to add another platform to the list and have the resources to maintain it, send a message to the Mobicents Contributors Forum
 

How To Setup Continuous Builds?

Line: 30 to 30
 The CC file is named
config.xml
. It uses the ant script build-mobicents24.xml and the modified server startup script run-cc.sh.
Changed:
<
<

Nightly run of Unit Test Suite

>
>

Nightly run of JUnit Test Suite

 This is a pending task. Post on the forums if you are interested to help with it.

 <<O>>  Difference Topic MobicentsQA (12 - 23 Dec 2005 - Main.ivelin)
Line: 1 to 1
 
META TOPICPARENT name="MobicentsOpenSLEE"

Mobicents Quality Assurance

Line: 21 to 21
 
Added:
>
>
The results for Solaris 9, JDK 1.4.2 can be found on the designated mailing list. They are executed on Sun Netra 440, which is a popular carrier grade server:
 

How To Setup Continuous Builds?

The continuous build and test run are based on a Cruise Control script. It can be found in the Mobicents CVS repository under /scripts/.


 <<O>>  Difference Topic MobicentsQA (11 - 19 Dec 2005 - Main.ivelin)
Line: 1 to 1
 
META TOPICPARENT name="MobicentsOpenSLEE"

Mobicents Quality Assurance

Line: 9 to 9
 

Continuous Builds

After each CVS check-in, the build system automatically rebuilds the full source tree to ensure source code integrity. The reports can be found at:

Deleted:
<
<
 http://proxenet.u-strasbg.fr:8080/cruisecontrol/buildresults/mobicents
Deleted:
<
<

How To Setup Continuous Builds?

The continuous build and test run are based on a Cruise Control script. It can be found in the Mobicents CVS repository under /scripts/.

The CC file is named

config.xml
. It uses the ant script build-mobicents24.xml and the modified server startup script run-cc.sh.
 

Nightly run of SLEE TCK (Technology Compatibility Kit)

Once a day the latest source tree (CVS HEAD) is automatically checked out and tested against the TCK.

Line: 28 to 21
 
Added:
>
>

How To Setup Continuous Builds?

The continuous build and test run are based on a Cruise Control script. It can be found in the Mobicents CVS repository under /scripts/.

The CC file is named

config.xml
. It uses the ant script build-mobicents24.xml and the modified server startup script run-cc.sh.
 

Nightly run of Unit Test Suite

This is a pending task. Post on the forums if you are interested to help with it.


 <<O>>  Difference Topic MobicentsQA (10 - 09 Dec 2005 - Main.ivelin)
Line: 1 to 1
 
META TOPICPARENT name="MobicentsOpenSLEE"

Mobicents Quality Assurance

Line: 44 to 44
  -- Main.ivelin - 08 May 2005
Added:
>
>

 <<O>>  Difference Topic MobicentsQA (9 - 07 Dec 2005 - Main.ivelin)
Line: 1 to 1
 
META TOPICPARENT name="MobicentsOpenSLEE"

Mobicents Quality Assurance

Line: 30 to 30
 

Nightly run of Unit Test Suite

Changed:
<
<
This is scheduled to be implemented as soon as we reach 100% pass rate on the TCK. As of May 8, 2005, we are at around 80%.
>
>
This is a pending task. Post on the forums if you are interested to help with it.

Build Result Archives

Results from each continuous build are sent to a designated mailing list, which is regularly archived.

 

Performance Testing and Benchmarking


 <<O>>  Difference Topic MobicentsQA (8 - 06 Oct 2005 - Main.ivelin)
Line: 1 to 1
 
META TOPICPARENT name="MobicentsOpenSLEE"

Mobicents Quality Assurance

Thanks to Emil Ivov, The Mobicents project has coninuously running build and test systems.

Added:
>
>
 

Continuous Builds

After each CVS check-in, the build system automatically rebuilds the full source tree to ensure source code integrity. The reports can be found at:


 <<O>>  Difference Topic MobicentsQA (7 - 30 Sep 2005 - Main.ivelin)
Line: 1 to 1
 
META TOPICPARENT name="MobicentsOpenSLEE"

Mobicents Quality Assurance

Line: 10 to 10
 http://proxenet.u-strasbg.fr:8080/cruisecontrol/buildresults/mobicents
Added:
>
>

How To Setup Continuous Builds?

The continuous build and test run are based on a Cruise Control script. It can be found in the Mobicents CVS repository under /scripts/.

The CC file is named

config.xml
. It uses the ant script build-mobicents24.xml and the modified server startup script run-cc.sh.
 

Nightly run of SLEE TCK (Technology Compatibility Kit)

Once a day the latest source tree (CVS HEAD) is automatically checked out and tested against the TCK.


 <<O>>  Difference Topic MobicentsQA (6 - 17 Sep 2005 - Main.ivelin)
Line: 1 to 1
 
META TOPICPARENT name="MobicentsOpenSLEE"

Mobicents Quality Assurance

Line: 16 to 16
 The results for Linux are published at:
Changed:
<
<
>
>
 

Nightly run of Unit Test Suite


 <<O>>  Difference Topic MobicentsQA (5 - 16 Aug 2005 - Main.ivelin)
Line: 1 to 1
 
META TOPICPARENT name="MobicentsOpenSLEE"

Mobicents Quality Assurance

Line: 12 to 12
 

Nightly run of SLEE TCK (Technology Compatibility Kit)

Changed:
<
<
Once a day the latest source tree (CVS HEAD) is automatically checked out and tested against the TCK. The results are published at:
>
>
Once a day the latest source tree (CVS HEAD) is automatically checked out and tested against the TCK.

The results for Linux are published at:

 

 <<O>>  Difference Topic MobicentsQA (4 - 15 Aug 2005 - Main.ivelin)
Line: 1 to 1
 
META TOPICPARENT name="MobicentsOpenSLEE"

Mobicents Quality Assurance

Line: 14 to 14
 Once a day the latest source tree (CVS HEAD) is automatically checked out and tested against the TCK. The results are published at:
Changed:
<
<
>
>
 

Nightly run of Unit Test Suite


 <<O>>  Difference Topic MobicentsQA (3 - 26 Jul 2005 - Main.ivelin)
Line: 1 to 1
 
META TOPICPARENT name="MobicentsOpenSLEE"

Mobicents Quality Assurance

Line: 22 to 22
 This is scheduled to be implemented as soon as we reach 100% pass rate on the TCK. As of May 8, 2005, we are at around 80%.
Added:
>
>

Performance Testing and Benchmarking

 -- Main.ivelin - 08 May 2005

 <<O>>  Difference Topic MobicentsQA (2 - 08 Jun 2005 - Main.emcho)
Line: 1 to 1
 
META TOPICPARENT name="MobicentsOpenSLEE"

Mobicents Quality Assurance

Line: 16 to 16
 
Added:
>
>
 

Nightly run of Unit Test Suite


 <<O>>  Difference Topic MobicentsQA (1 - 08 May 2005 - Main.ivelin)
Line: 1 to 1
Added:
>
>
META TOPICPARENT name="MobicentsOpenSLEE"

Mobicents Quality Assurance

Thanks to Emil Ivov, The Mobicents project has coninuously running build and test systems.

Continuous Builds

After each CVS check-in, the build system automatically rebuilds the full source tree to ensure source code integrity. The reports can be found at:

http://proxenet.u-strasbg.fr:8080/cruisecontrol/buildresults/mobicents

Nightly run of SLEE TCK (Technology Compatibility Kit)

Once a day the latest source tree (CVS HEAD) is automatically checked out and tested against the TCK. The results are published at:

Nightly run of Unit Test Suite

This is scheduled to be implemented as soon as we reach 100% pass rate on the TCK. As of May 8, 2005, we are at around 80%.

-- Main.ivelin - 08 May 2005


Topic MobicentsQA . { View | Diffs r15 < r14 < r13 < r12 | More }
 XML java.net RSS