add component path analyzer to allow searching for components by name… #190
GitHub Actions / lucee@6 Test Results
failed
Sep 25, 2024 in 0s
2 fail, 324 pass in 1m 19s
Annotations
Check warning on line 0 in tests.specs.unit.AppenderServiceTest
github-actions / lucee@6 Test Results
Tests detached appenders Perform actions on detached appender Tests the ability to log a single raw message to the appender (tests.specs.unit.AppenderServiceTest) failed
test-harness/tests/results/test-results-junit.xml [took 0s]
Raw output
Expected [2] but received [1]
122: true
123: );
124: expect( getDataStreamCount( appender.getProperty( "dataStreamPattern" ) ) ).toBe( dataStreamCount + 1 );
125: } );
126:
/home/runner/work/cbelasticsearch/cbelasticsearch/test-harness/tests/specs/unit/AppenderServiceTest.cfc:124
Check warning on line 0 in tests.specs.unit.AppenderServiceTest
github-actions / lucee@6 Test Results
Tests detached appenders Perform actions on detached appender Tests the ability to log a multiple raw message to the appender (tests.specs.unit.AppenderServiceTest) failed
test-harness/tests/results/test-results-junit.xml [took 0s]
Raw output
Expected [11] but received [1]
135: true
136: );
137: expect( getDataStreamCount( appender.getProperty( "dataStreamPattern" ) ) ).toBe( dataStreamCount + variables.testEntries.len() );
138: } );
139:
/home/runner/work/cbelasticsearch/cbelasticsearch/test-harness/tests/specs/unit/AppenderServiceTest.cfc:137
Loading