You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since I would like to share repositories between Pharo and GemStone, by using the Monticello package convention, I would like to share tests between these two. Of course, the syntax is different so I need to adjust the tests for GemStone.
What is the best way to share tests between Pharo and GemStone (I'll have to most probably make some subtle changes to the code along the way)? I could test for the platform the test is running, but that seems to be cumbersome way to do it. Is there better way to do it?
Thank you for any suggestions.
The text was updated successfully, but these errors were encountered:
To share code between Pharo and GemStone you'll need to create a BaselineOf for Pharo and simply add the shared packages to the proper Test component or Core component structure for Rowan V3 (as I described earlier)[https://github.com/GemTalk/JadeiteForPharo/issues/217#issuecomment-2651642559]... Rowan will ignore packages (including the BaselineOf) in the src directory that are not managed by the Rowan 3 meta data ... so it really is only necessary to worry about the GemStone packages in Rowan ..
Rowan can handle platform conditionals as well (see Rowan:spec_0024)[https://github.com/dalehenrich/RowanSample9V3/tree/spec_0024], but that will only be necessary when/if Rowan is ported to Pharo ...
Hello @dalehenrich ,
Since I would like to share repositories between Pharo and GemStone, by using the
Monticello
package convention, I would like to share tests between these two. Of course, the syntax is different so I need to adjust the tests for GemStone.What is the best way to share tests between Pharo and GemStone (I'll have to most probably make some subtle changes to the code along the way)? I could test for the platform the test is running, but that seems to be cumbersome way to do it. Is there better way to do it?
Thank you for any suggestions.
The text was updated successfully, but these errors were encountered: