Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [papyrus-rt-dev] Papyrus-RT automated testing

Hi,

 

I just added the “publish results” configuration in the job [1] so after the next run you should get a test result entry ( like in [2], exactly the same one as junit test)

 

Regards,

Benoît

 

[1] https://hudson.eclipse.org/papyrus-rt/job/Papyrus-RT-Master-RCPTT/

[2] https://hudson.eclipse.org/papyrus/job/papyrus-rcptt-gerrit/

 

 

De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] De la part de Remi Schnekenburger
Envoyé : mercredi 5 avril 2017 17:23
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>
Objet : Re: [papyrus-rt-dev] Papyrus-RT automated testing

 

Hi Charles,

 

The tests suites on the master build are JUnit based, and as so, target mainly the basic testing.

 

On the other hand, RCPTT waits for a Papyrus-RT product to be build, to test all components alltogether. So It runs test scenarios as they would be done by end users. Currently, the implementation of the RCPTT tests is more a proof of concept than real test cover of all scenarios.

Here is the list of the 15 tests ran by the job:

 [INFO] Pass 1 (15) processed. 0 failed. spent: 0:39, 2:49 mins remaining. CallEvent_10_CallEventCreationTest. time: 38993ms

[INFO] Pass 2 (15) processed. 0 failed. spent: 0:54, 2:42 mins remaining. CallEvent_20_MessageDeletionTest. time: 14604ms 
[INFO] Pass 3 (15) processed. 0 failed. spent: 1:10, 2:34 mins remaining. Capsule_10_IsDirectEdittedInModelExplorer. time: 15262ms 
[INFO] Pass 4 (15) processed. 0 failed. spent: 1:13, 2:01 mins remaining. Init_00_ViewPointTest. time: 3247ms 
[INFO] Pass 5 (15) processed. 0 failed. spent: 1:18, 1:40 mins remaining. Init_01_New Papyrus Project. time: 4708ms 
[INFO] Pass 6 (15) processed. 0 failed. spent: 1:32, 1:32 mins remaining. Init_10_CapsuleCreation. time: 13132ms 
[INFO] Pass 7 (15) processed. 0 failed. spent: 1:51, 1:26 mins remaining. Port_30_SetPortKind. time: 19399ms 
[INFO] Pass 8 (15) processed. 0 failed. spent: 2:04, 1:14 mins remaining. ProtocolMessage_10_SelectedInModelExplorer. time: 12004ms 
[INFO] Pass 9 (15) processed. 0 failed. spent: 2:20, 1:03 mins remaining. Synchro_30_SynchroValueInPropertyView. time: 16392ms 
[INFO] Pass 10 (15) processed. 0 failed. spent: 2:34, 0:51 mins remaining. Synchro_31_SynchronizationOfPort. time: 13808ms 
[INFO] Pass 11 (15) processed. 0 failed. spent: 2:51, 0:39 mins remaining. Synchro_32_SynchronizationOfCapsulePart. time: 16407ms 
[INFO] Pass 12 (15) processed. 0 failed. spent: 3:14, 0:27 mins remaining. SystemProtocolPort_10_FromModelExplorer. time: 22304ms 
[INFO] Pass 13 (15) processed. 0 failed. spent: 3:33, 0:14 mins remaining. SystemProtocolPort_10_TestCreationFromPalette. time: 18748ms 
[INFO] Pass 14 (15) processed. 0 failed. spent: 3:56, 0:00 mins remaining. SystemProtocolPort_11_FromModelExplorer. time: 23046ms 
[INFO] Pass 15 (15) processed. 0 failed. spent: 4:08, 0:00 mins remaining. SystemProtocolPort_11_TestCreationFromPalette. time: 11513ms 
 
That covers some of graphical editing (renaming in model explorer, creating a system protocol port from various views, model wizard, etc.). 
 
On the wiki page for Papyrus-RT, you may find some information on the usage of RCPTT for Papyrus-RT testing. That was ran in common with other papyrus projects, to try to share some of the basic knowledge and procedures [1] 
 
Cheers,
Rémi
 
[1] https://wiki.eclipse.org/Papyrus/Tester/RCPTT
 

 

2017-04-05 17:13 GMT+02:00 charles+zeligsoft.com <charles@xxxxxxxxxxxxx>:

All,

 

I hope someone can help me with this subject topic…

 

I already found a lot of good information regarding automated testing as part of the Papyrus-RT-Master build, including the test suites, lists, and results.

 

I also found the Papyrus-RT-Master-RCPTT Build, but that one is much more opaque as to what it is doing… Would you know whether there are there RCPTT tests being run as part of that build? The log’s raw output seems to indicate this, but that is rather cryptic (and I can no longer access the information because of an expired certificate…). Would you know of any documentation with regards to those tests?

 

 

Thank you!

 

 

Regards,

 

Charles Rivet
Senior Product Manager, Papyrus-RT product leader

 


_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev



 

--

Remi Schnekenburger

Senior Software Architect / General Manager

EclipseSource Paris

Email: rschnekenburger@xxxxxxxxxxxxxxxxx
Web:
http://eclipsesource.com/paris 
Phone: +33 1 85 41 08 65

German Phone: +49 89 21 555 30 - 25

Fax: +49 89 21 555 30 - 19

Hangouts: rschnekenburger@xxxxxxxxxxxxxxxxx

EclipseSource France SAS

7 rue de la Croix Martre
91120 Palaiseau

General Manager: Remi Schnekenburger

Registered Office: 7 rue de la Croix Martre, 91120 Palaiseau, France

Commercial Register 824 977 516  R.C.S. EVRY


Back to the top