Major refactoring

.github/workflows/default.yml

@@ -33,7 +33,10 @@ jobs:
           skip-build-cache: true
 
       - name: Test
-        run: go test -race -v -coverprofile=coverage.out  -covermode=atomic ./...
+        run: go test -race -v -coverprofile=coverage_temp.out  -covermode=atomic ./...
+
+      - name: Remove mocks and cmd from coverage
+        run: grep -v -e "/cemd/mocks/" -e "/cemd/cmd/" coverage_temp.out > coverage.out
 
       - name: Send coverage
         uses: coverallsapp/github-action@v2

.mockery.yaml

@@ -0,0 +1,10 @@
+with-expecter: true
+inpackage: false
+dir: "{{ .InterfaceDir }}/mocks/"
+mockname: "{{.InterfaceName}}"
+outpkg: "mocks"
+filename: "{{.InterfaceName}}.go"
+all: true
+packages:
+  github.com/enbility/cemd/api:
+  github.com/enbility/cemd/evsecc:

api/api.go

@@ -1,13 +1,54 @@
 package api
 
 import (
-	shipapi "github.com/enbility/ship-go/api"
+	spineapi "github.com/enbility/spine-go/api"
+	"github.com/enbility/spine-go/model"
 )
 
-// Implemented by *Solutions, used by Cem
-type SolutionInterface interface {
-	RegisterRemoteDevice(details *shipapi.ServiceDetails, dataProvider any) any
-	UnRegisterRemoteDevice(remoteDeviceSki string)
+//go:generate mockery
+
+// Implemented by CEM
+type CemInterface interface {
+	// Setup the EEBUS service
+	Setup() error
+
+	// Start the EEBUS service
+	Start()
+
+	// Shutdown the EEBUS service
+	Shutdown()
+
+	// Add a use case implementation
+	AddUseCase(usecase UseCaseInterface)
+}
+
+// Implemented by each UseCase
+type UseCaseInterface interface {
+	// provide the usecase name
+	UseCaseName() model.UseCaseNameType
+
+	// add the features
 	AddFeatures()
-	AddUseCases()
+
+	// add the usecase
+	AddUseCase()
+
+	// returns if the entity supports the usecase
+	//
+	// possible errors:
+	//   - ErrDataNotAvailable if that information is not (yet) available
+	//   - and others
+	IsUseCaseSupported(remoteEntity spineapi.EntityRemoteInterface) (bool, error)
+}
+
+// interface for informing the cem about specific events
+// for each supported usecase
+//
+// UseCaseEventType values can be found in the api definition of each
+// supported usecase
+//
+// implemented by the actual CEM, used by UCEvseCCInterface implementation
+type UseCaseEventReaderInterface interface {
+	// Inform about a new usecase specific event
+	SpineEvent(ski string, entity spineapi.EntityRemoteInterface, event UseCaseEventType)
 }