Too many tests executed

[marceltaeumel]

The detection of which tests to execute seems to fetch too many tests---even some of dependent projects.

[fniephaus]

As far as I know, it just executes all TestCases it can find.
Some students were also looking for a way to exclude tests. So I guess it'd be good to somehow define which tests should be executed rather than just executing them all.

[fniephaus]

I believe this is the code we want to look at:

builderCI/scripts/MetacelloBuilderTravisCI.st

Lines 61 to 75 in eba65fc

	!MetacelloBuilderTravisCI class methodsFor: 'test harness' stamp: 'dkh 9/4/2012 18:31'!
	runHarnessFor: configurationClassNameList successFilename: successFilename failFilename: failFilename
	[
	| suite result resultsFileName |
	suite := TestCase suiteClass named: configurationClassNameList printString , ' Test Suite'.
	configurationClassNameList
	do: [ :className |
	(((Smalltalk at: #'MetacelloProjectRegistration')
	registrationForClassNamed: className
	ifAbsent: [ self error: className printString , ' not registered (loaded)' ])
	currentlyLoadedClassesInProject select: [ :cl | cl inheritsFrom: TestCase ])
	do: [ :cl |
	cl isAbstract
	ifFalse: [ suite addTest: cl buildSuiteFromSelectors ] ] ].
	result := suite run.

[marceltaeumel]

Yes, this is the code that I executed in the screenshot. ;) I am wondering how Metacello determines loaded classes at all.

[fniephaus]

Looks like it's following dependencies, but let's wait for @dalehenrich's reply...

[dalehenrich]

This is intentional. The idea is that the test cases loaded as a result of
loading the configuration be run.

This is the way TravisCIHarness works, but I would certainly entertain
different test specification schemes.

Dale

On Fri, Aug 8, 2014 at 5:23 AM, Fabio Niephaus notifications@github.com
wrote:

Looks like it's following dependencies, but let's wait for @dalehenrich
https://github.com/dalehenrich's reply...

—
Reply to this email directly or view it on GitHub
#70 (comment)
.