Comment #4 on issue 3179 by cy.delau...@gmail.com: Failing Tests for Monticello http://code.google.com/p/pharo/issues/detail?id=3179 I join a changeSet that make all monticello test green. For that, I made the fix provided by stephane in issue 2294 (see above), and fix the remaining test: MCChangeNotificationTest >> testExtMethodModified. That's the method I modified to solve the problem: mockClassExtension "I change the protocol of this method (to be '*monticellomocks' instead of 'mocks') to resolve the failing test: MCChangeNotificationTest >> testExtMethodModified. This test basically test that when we modified an extension method, the extended package is marked as 'modified'. The problem is that Monticello treat differently a classic method from an extension method, and this only by checking if the protocol name start with a star. Therefore, if the protocol does not match the extending package name, the extending package name will never be notified, and the test will fail. " Attachments: issue3179.1.cs 3.1 KB

Updates: Status: Closed Comment #6 on issue 3179 by marcus.d...@gmail.com: Failing Tests for Monticello http://code.google.com/p/pharo/issues/detail?id=3179 13008

Updates: Status: Fixed Labels: -Milestone-1.2 Comment #8 on issue 3179 by marcus.d...@gmail.com: Failing Tests for Monticello http://code.google.com/p/pharo/issues/detail?id=3179 I added it to 1.2... TODO: add FixingMonticelloTestFailingInHudson.1.cs to 1.3 (and on close tag this report 1.2 again)