Posted by Jan Vrany on Sep 18, 2012; 3:44pm
URL: https://forum.world.st/Smalltalk-X-port-of-Metacello-tp4647981p4647992.html

On 18/09/12 16:30, Dale Henrichs wrote:
> Jan,
>
> Great news!
>
> The vast majority of the tests are associated with the MC packages ... when you take the mcz packages out of the equation there isn't too much to test ... The bulk of the MC tests are doing loads of test packages to test the various features.
>

If you say so...

I tried to create very simple config like:

version0_0_1: spec
     <version: '0.0.1'>

     spec for: #common do:[
         spec package: 'stx:goodies/metacello'.
     ]


and then tried just to inspect

ConfigurationOfMetacello project version: '0.0.1'

and ended up with DNUs. I tried to naively fix them, but more appeared.
I would say this should work without any fancy MC stuff, shouldn't it?

> Last week I did some work to move some of the code that deserves to be in core from MC and I ended up pushing some more tests towards core, but that work was done on the master branch and I noticed that you based your work on the 1.0-beta.31.1.5 branch. You should probably move your port to the master branch as a start.

OK.  I'll update and try it again.


>
> We should start considering a generic package test layer ... a bunch of the load tests from MC could be moved into this layer. The details of the test are not specific to Monticello, but you have to have a package loader implemented to run the tests ... I would want to do this work off of the master branch.
>
> I will also need to get busy on the new Cypress implementation ...

:-) Yes. We will see how it works in real



Jan