Expose Account query API #97
GitHub Actions / Test Reports
succeeded
Aug 6, 2024 in 0s
297 passed, 0 failed and 0 skipped
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.account.adapter.web.AccountControllerSpec.xml
4 tests were completed in 2s with 4 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.account.adapter.web.AccountControllerSpec | 4✅ | 2s |
✅ io.myfinbox.account.adapter.web.AccountControllerSpec
✅ should create an new account with default locale
✅ should fail to create an account when request has validation failures
✅ should gen one account when exits
✅ should get not found when account doesn't exit
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.account.application.CreateAccountServiceSpec.xml
33 tests were completed in 73ms with 33 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.account.application.CreateAccountServiceSpec | 33✅ | 73ms |
✅ io.myfinbox.account.application.CreateAccountServiceSpec
✅ should fail account creation when firstName length exceeds limit
✅ should fail account creation when lastName length exceeds limit
✅ should fail account creation when email address is invalid with message: 'Email address cannot be empty.'
✅ should fail account creation when email address is invalid with message: 'Email address cannot be empty.'
✅ should fail account creation when email address is invalid with message: 'Email address cannot be empty.'
✅ should fail account creation when email address is invalid with message: 'Email address must follow RFC 5322 standard.'
✅ should fail account creation when email address is invalid with message: 'Email address must follow RFC 5322 standard.'
✅ should fail account creation when email address is invalid with message: 'Email address must follow RFC 5322 standard.'
✅ should fail account creation when email address is invalid with message: 'Email address must follow RFC 5322 standard.'
✅ should fail account creation when email address is invalid with message: 'Email address must follow RFC 5322 standard.'
✅ should fail account creation when email address is invalid with message: 'Email address must follow RFC 5322 standard.'
✅ should fail account creation when email address is invalid with message: 'Email address must follow RFC 5322 standard.'
✅ should fail account creation when email address is invalid with message: 'Email address must follow RFC 5322 standard.'
✅ should fail account creation when email address is invalid with message: 'Email address must follow RFC 5322 standard.'
✅ should fail account creation when email address is invalid with message: 'Email address must follow RFC 5322 standard.'
✅ should fail account creation when email address is invalid with message: 'Email address must follow RFC 5322 standard.'
✅ should fail account creation when email address is invalid with message: 'Email address must follow RFC 5322 standard.'
✅ should fail account creation when email address is invalid with message: 'Email address must follow RFC 5322 standard.'
✅ should fail account creation when email address is invalid with message: 'Email address must follow RFC 5322 standard.'
✅ should fail account creation when email address is invalid with message: 'Email address must follow RFC 5322 standard.'
✅ should fail account creation when email address is invalid with message: 'Email address length cannot exceed '255' characters.'
✅ should fail account creation when email address is invalid with message: '#errorMessage'
✅ should fail account creation when currency is invalid with message: 'Currency 'null' is invalid.'
✅ should fail account creation when currency is invalid with message: 'Currency '' is invalid.'
✅ should fail account creation when currency is invalid with message: 'Currency ' ' is invalid.'
✅ should fail account creation when currency is invalid with message: 'Currency 'MD' is invalid.'
✅ should fail account creation when currency is invalid with message: '#errorMessage'
✅ should fail account creation when zoneId is invalid with message: 'ZoneId 'null' is invalid.'
✅ should fail account creation when zoneId is invalid with message: 'ZoneId '' is invalid.'
✅ should fail account creation when zoneId is invalid with message: 'ZoneId ' ' is invalid.'
✅ should fail account creation when zoneId is invalid with message: 'ZoneId 'Europe/Chissinau' is invalid.'
✅ should fail account creation when zoneId is invalid with message: '#errorMessage'
✅ should create an account successfully
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.expense.adapter.messaging.AccountEventsListenerSpec.xml
1 tests were completed in 21s with 1 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.expense.adapter.messaging.AccountEventsListenerSpec | 1✅ | 21s |
✅ io.myfinbox.expense.adapter.messaging.AccountEventsListenerSpec
✅ should create default expense categories on account created event
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.expense.adapter.web.ExpenseCategoryControllerSpec.xml
6 tests were completed in 4s with 6 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.expense.adapter.web.ExpenseCategoryControllerSpec | 6✅ | 4s |
✅ io.myfinbox.expense.adapter.web.ExpenseCategoryControllerSpec
✅ Should create a new category expense
✅ should fail creation when request has validation failures
✅ should update an existing category expense name
✅ Should fail update when category not found
✅ should delete an expense category
✅ Should fail delete when expense category is in use
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.expense.adapter.web.ExpenseControllerSpec.xml
6 tests were completed in 3s with 6 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.expense.adapter.web.ExpenseControllerSpec | 6✅ | 3s |
✅ io.myfinbox.expense.adapter.web.ExpenseControllerSpec
✅ should create a new expense
✅ should fail creation when request has validation failures
✅ should update an expense
✅ should fail updating when provided category not found
✅ should delete an expense
✅ should fail delete when expense not found
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.expense.application.CreateExpenseServiceSpec.xml
18 tests were completed in 110ms with 18 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.expense.application.CreateExpenseServiceSpec | 18✅ | 110ms |
✅ io.myfinbox.expense.application.CreateExpenseServiceSpec
✅ should fail expense creation when accountId is null
✅ should fail expense creation when categoryId is null
✅ should fail expense creation when paymentType is invalid [paymentType: null, failMessage: PaymentType must be 'Cash' or 'Card'., #0]
✅ should fail expense creation when paymentType is invalid [paymentType: , failMessage: PaymentType must be 'Cash' or 'Card'., #1]
✅ should fail expense creation when paymentType is invalid [paymentType: Hola, failMessage: PaymentType must be 'Cash' or 'Card'., #2]
✅ should fail expense creation when paymentType is invalid
✅ should fail expense creation when amount is invalid [value: null, failMessage: Amount cannot be null., #0]
✅ should fail expense creation when amount is invalid [value: 0.0, failMessage: Amount must be a positive value., #1]
✅ should fail expense creation when amount is invalid [value: -25.56, failMessage: Amount must be a positive value., #2]
✅ should fail expense creation when amount is invalid
✅ should fail expense creation when currencyCode is invalid [currencyCode: null, failMessage: CurrencyCode cannot be null., #0]
✅ should fail expense creation when currencyCode is invalid [currencyCode: , failMessage: CurrencyCode is not valid., #1]
✅ should fail expense creation when currencyCode is invalid [currencyCode: US, failMessage: CurrencyCode is not valid., #2]
✅ should fail expense creation when currencyCode is invalid [currencyCode: MDLA, failMessage: CurrencyCode is not valid., #3]
✅ should fail expense creation when currencyCode is invalid
✅ should fail expense creation when expenseDate is null
✅ should fail expense creation when category is not found
✅ should create an expense
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.expense.application.DefaultCategoryServiceSpec.xml
25 tests were completed in 290ms with 25 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.expense.application.DefaultCategoryServiceSpec | 25✅ | 290ms |
✅ io.myfinbox.expense.application.DefaultCategoryServiceSpec
✅ should fail to create default categories when account is null
✅ should successfully create default categories for the provided account
✅ should fail category creation when accountId is null
✅ should fail category creation when name is not valid [categoryName: null, failMessage: Name cannot be empty., #0]
✅ should fail category creation when name is not valid [categoryName: , failMessage: Name cannot be empty., #1]
✅ should fail category creation when name is not valid [categoryName: , failMessage: Name cannot be empty., #2]
✅ should fail category creation when name is not valid [categoryName: oqE5tvYHfvi3eEFrt40YrGhKjuPoiXKCkDUxpS2Df7lMN1oryA0widXYsvs2aY9y9oKuvFiS5xl99REAwh7yppPezvram6NpOKkIvjMUsGveJu3TZ25XrpZhUcGdRW2wFomJ6toaSGKpxzeU2eS0SX5BHCJQCNzCE5qzUhC7vloajtWyc0tZIvf588c6BBhXyzBpANLmL4PLGTSmSo0QGqs8TBPrWaoKxkHvVH0aoucjeInTD5ZRK7ViurTNCfyN, failMessage: Name length cannot exceed 100 characters., #3]
✅ should fail category creation when name is not valid
✅ should fail category creation when name is duplicate
✅ should successfully create a new expense category
✅ should fail category update when accountId is null
✅ should fail category update when name is not valid [categoryName: null, failMessage: Name cannot be empty., #0]
✅ should fail category update when name is not valid [categoryName: , failMessage: Name cannot be empty., #1]
✅ should fail category update when name is not valid [categoryName: , failMessage: Name cannot be empty., #2]
✅ should fail category update when name is not valid [categoryName: uUpPBssy2j3jKpcGiJI62c5OTFC1sg9Pxe54pMWV6fJlxqdLbcUJSRYERco4le2KcmMVZ0uuPpveTO88ky7gfbOUH4hMu3NJp3AlOZPW40X33k8c6SJge98F6ojtdcr15q17hL6sKgALa6hWkwbtPdQhLEfm9WBfacCxSmZ3G4NHZobI29sB1rlmFa2QBnCg9SKXNKZByRvKImFR3iijJt2hKa3EwPcFGD38h4cHOURXGlLBhtcNcPk5nywO9Qam, failMessage: Name length cannot exceed 100 characters., #3]
✅ should fail category update when name is not valid
✅ should fail category update when category not found, null categoryId
✅ should fail category update when category not found, no DB existence
✅ should not update category name when name not changed
✅ should fail category update when name is duplicate
✅ should update an existing expense category with a new name
✅ should fail to delete category when category not found, categoryId is null
✅ should fail to delete category when category not found in the database
✅ should fail to delete category when category is in use
✅ should successfully delete a category when no expenses are associated with it
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.expense.application.DeleteExpenseServiceSpec.xml
3 tests were completed in 25ms with 3 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.expense.application.DeleteExpenseServiceSpec | 3✅ | 25ms |
✅ io.myfinbox.expense.application.DeleteExpenseServiceSpec
✅ should fail delete when expense id is null
✅ should fail delete when expense not found
✅ should delete an expense
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.expense.application.UpdateExpenseServiceSpec.xml
20 tests were completed in 1s with 20 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.expense.application.UpdateExpenseServiceSpec | 20✅ | 1s |
✅ io.myfinbox.expense.application.UpdateExpenseServiceSpec
✅ should fail expense updating when accountId is null
✅ should fail expense updating when categoryId is null
✅ should fail expense updating when paymentType is invalid [paymentType: null, failMessage: PaymentType must be 'Cash' or 'Card'., #0]
✅ should fail expense updating when paymentType is invalid [paymentType: , failMessage: PaymentType must be 'Cash' or 'Card'., #1]
✅ should fail expense updating when paymentType is invalid [paymentType: Hola, failMessage: PaymentType must be 'Cash' or 'Card'., #2]
✅ should fail expense updating when paymentType is invalid
✅ should fail expense updating when amount is invalid [value: null, failMessage: Amount cannot be null., #0]
✅ should fail expense updating when amount is invalid [value: 0.0, failMessage: Amount must be a positive value., #1]
✅ should fail expense updating when amount is invalid [value: -25.56, failMessage: Amount must be a positive value., #2]
✅ should fail expense updating when amount is invalid
✅ should fail expense updating when currencyCode is invalid [currencyCode: null, failMessage: CurrencyCode cannot be null., #0]
✅ should fail expense updating when currencyCode is invalid [currencyCode: , failMessage: CurrencyCode is not valid., #1]
✅ should fail expense updating when currencyCode is invalid [currencyCode: US, failMessage: CurrencyCode is not valid., #2]
✅ should fail expense updating when currencyCode is invalid [currencyCode: MDLA, failMessage: CurrencyCode is not valid., #3]
✅ should fail expense updating when currencyCode is invalid
✅ should fail expense updating when expenseDate is null
✅ should fail expense updating when expense ID is null
✅ should fail expense updating when expense is not found
✅ should fail expense updating when expense category is not found
✅ should update an expense
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.income.adapter.messaging.AccountEventsListenerSpec.xml
1 tests were completed in 2s with 1 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.income.adapter.messaging.AccountEventsListenerSpec | 1✅ | 2s |
✅ io.myfinbox.income.adapter.messaging.AccountEventsListenerSpec
✅ should create default income sources on account created event
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.income.adapter.web.IncomeControllerSpec.xml
6 tests were completed in 2s with 6 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.income.adapter.web.IncomeControllerSpec | 6✅ | 2s |
✅ io.myfinbox.income.adapter.web.IncomeControllerSpec
✅ should create a new income
✅ should fail creation when request has validation failures
✅ should update an income
✅ should fail updating when provided income source not found
✅ should delete an income
✅ should fail delete when income not found
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.income.adapter.web.IncomeSourceControllerSpec.xml
6 tests were completed in 101ms with 6 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.income.adapter.web.IncomeSourceControllerSpec | 6✅ | 101ms |
✅ io.myfinbox.income.adapter.web.IncomeSourceControllerSpec
✅ should create a new income source
✅ should fail income source creation when request has validation failures
✅ should update an existing income source name
✅ Should fail update when income source not found
✅ should delete an income source
✅ Should fail delete when income source is in use
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.income.application.CreateIncomeServiceSpec.xml
18 tests were completed in 81ms with 18 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.income.application.CreateIncomeServiceSpec | 18✅ | 81ms |
✅ io.myfinbox.income.application.CreateIncomeServiceSpec
✅ should fail income creation when accountId is null
✅ should fail income creation when incomeSourceId is null
✅ should fail income creation when paymentType is invalid [paymentType: null, failMessage: PaymentType must be 'Cash' or 'Card'., #0]
✅ should fail income creation when paymentType is invalid [paymentType: , failMessage: PaymentType must be 'Cash' or 'Card'., #1]
✅ should fail income creation when paymentType is invalid [paymentType: Hola, failMessage: PaymentType must be 'Cash' or 'Card'., #2]
✅ should fail income creation when paymentType is invalid
✅ should fail income creation when amount is invalid [value: null, failMessage: Amount cannot be null., #0]
✅ should fail income creation when amount is invalid [value: 0.0, failMessage: Amount must be a positive value., #1]
✅ should fail income creation when amount is invalid [value: -25.56, failMessage: Amount must be a positive value., #2]
✅ should fail income creation when amount is invalid
✅ should fail income creation when currencyCode is invalid [currencyCode: null, failMessage: CurrencyCode cannot be null., #0]
✅ should fail income creation when currencyCode is invalid [currencyCode: , failMessage: CurrencyCode is not valid., #1]
✅ should fail income creation when currencyCode is invalid [currencyCode: US, failMessage: CurrencyCode is not valid., #2]
✅ should fail income creation when currencyCode is invalid [currencyCode: MDLA, failMessage: CurrencyCode is not valid., #3]
✅ should fail income creation when currencyCode is invalid
✅ should fail income creation when incomeDate is null
✅ should fail income creation when income source is not found
✅ should create an income
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.income.application.DefaultIncomeSourceServiceSpec.xml
25 tests were completed in 99ms with 25 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.income.application.DefaultIncomeSourceServiceSpec | 25✅ | 99ms |
✅ io.myfinbox.income.application.DefaultIncomeSourceServiceSpec
✅ should fail create default income sources when account is null
✅ should create income sources
✅ should fail income source creation when accountId is null
✅ should fail income source creation when name is not valid [incomeSourceName: null, failMessage: Name cannot be empty., #0]
✅ should fail income source creation when name is not valid [incomeSourceName: , failMessage: Name cannot be empty., #1]
✅ should fail income source creation when name is not valid [incomeSourceName: , failMessage: Name cannot be empty., #2]
✅ should fail income source creation when name is not valid [incomeSourceName: ApORPbjV6spytETUl11axbbVW2bX8zUcF2vofgzFVLKlKFuGjD8H0TPOtlLY5AnUyu3sqH0RehSohfaTPeYeMZQUUDNXDC8c6eTbsJmR2ywWWCja8Vj94reS0YYXvMYgdxam7CW0KuDmBVMVo9Zx0QeaJYxfRTxbRhkZas9vMY5oJJqNlsIRorZ71S7KI9aEzhsCjZ0oC2Y9KQkhgYad3LXJTdn7Vwm5NqOZ1Q21d8XcCA9z6Fuwm8ARSyiW5wh4, failMessage: Name length cannot exceed 100 characters., #3]
✅ should fail income source creation when name is not valid
✅ should fail income source creation when name is duplicate
✅ should successfully create a new income source
✅ should fail income source update when accountId is null
✅ should fail income source update when name is not valid [incomeSourceName: null, failMessage: Name cannot be empty., #0]
✅ should fail income source update when name is not valid [incomeSourceName: , failMessage: Name cannot be empty., #1]
✅ should fail income source update when name is not valid [incomeSourceName: , failMessage: Name cannot be empty., #2]
✅ should fail income source update when name is not valid [incomeSourceName: MYFHAX9mIu2EoECiULavsPBaPIarZCOiAHG96RZWaldequegteP5Gmw2gQonHLNRleURif3y3d15W1BWXh2cdDG2v3QPwNahvIpV3URZhrpz4nKNjCfm1c9zjdCa4ivJvCTWw2izyhzZPKNep3gW8KvVuEMYh6GNdvOFScadoADuvymylXXhhWdQl2LBtNmxR7yvrI2yuCSuC5f6OBio33kd2IK6lmQxxgnfGvsvlsd9TtvNcnCDBCPewZlKMky8, failMessage: Name length cannot exceed 100 characters., #3]
✅ should fail income source update when name is not valid
✅ should fail income source update when income source not found, null income source
✅ should fail income source update when income source not found, no DB existence
✅ should not update income source name when name not changed
✅ should fail income source update when name is duplicate
✅ should update an existing income source with a new name
✅ should fail to delete income source when income source not found, incomeSourceId is null
✅ should fail to delete income source when income source not found in the database
✅ should fail to delete income source when income source is in use
✅ should successfully delete a income source when no incomes are associated with it
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.income.application.DeleteIncomeServiceSpec.xml
3 tests were completed in 8ms with 3 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.income.application.DeleteIncomeServiceSpec | 3✅ | 8ms |
✅ io.myfinbox.income.application.DeleteIncomeServiceSpec
✅ should fail delete when income id is null
✅ should fail delete when income not found
✅ should delete an income
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.income.application.UpdateIncomeServiceSpec.xml
20 tests were completed in 43ms with 20 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.income.application.UpdateIncomeServiceSpec | 20✅ | 43ms |
✅ io.myfinbox.income.application.UpdateIncomeServiceSpec
✅ should fail income updating when accountId is null
✅ should fail income updating when incomeSourceId is null
✅ should fail income updating when paymentType is invalid [paymentType: null, failMessage: PaymentType must be 'Cash' or 'Card'., #0]
✅ should fail income updating when paymentType is invalid [paymentType: , failMessage: PaymentType must be 'Cash' or 'Card'., #1]
✅ should fail income updating when paymentType is invalid [paymentType: Hola, failMessage: PaymentType must be 'Cash' or 'Card'., #2]
✅ should fail income updating when paymentType is invalid
✅ should fail income updating when amount is invalid [value: null, failMessage: Amount cannot be null., #0]
✅ should fail income updating when amount is invalid [value: 0.0, failMessage: Amount must be a positive value., #1]
✅ should fail income updating when amount is invalid [value: -25.56, failMessage: Amount must be a positive value., #2]
✅ should fail income updating when amount is invalid
✅ should fail income updating when currencyCode is invalid [currencyCode: null, failMessage: CurrencyCode cannot be null., #0]
✅ should fail income updating when currencyCode is invalid [currencyCode: , failMessage: CurrencyCode is not valid., #1]
✅ should fail income updating when currencyCode is invalid [currencyCode: US, failMessage: CurrencyCode is not valid., #2]
✅ should fail income updating when currencyCode is invalid [currencyCode: MDLA, failMessage: CurrencyCode is not valid., #3]
✅ should fail income updating when currencyCode is invalid
✅ should fail income updating when incomeDate is null
✅ should fail income updating when income id null with income not found
✅ should fail income updating when income is not found
✅ should fail income updating when income source is not found
✅ should update an income
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.ModularitySpec.xml
2 tests were completed in 4s with 2 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.ModularitySpec | 2✅ | 4s |
✅ io.myfinbox.ModularitySpec
✅ should verify modular structure
✅ should write documentation snippets
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.ServerApplicationSpec.xml
1 tests were completed in 6ms with 1 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.ServerApplicationSpec | 1✅ | 6ms |
✅ io.myfinbox.ServerApplicationSpec
✅ should load contexts
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.shared.ApiExceptionHandlerSpec.xml
7 tests were completed in 469ms with 7 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.shared.ApiExceptionHandlerSpec | 7✅ | 469ms |
✅ io.myfinbox.shared.ApiExceptionHandlerSpec
✅ should get Bad Request when message not readable exception
✅ should get Bad Request when type mismatch exception
✅ should get Not Found when no handler found exception
✅ should get Method Not Allowed when request method not supported exception
✅ should get Not Acceptable when media type not acceptable exception
✅ should get Unsupported media type when media type not supported exception
✅ should get Internal Server Error when unexpected exception thrown
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.shared.ApiFailureHandlerSpec.xml
6 tests were completed in 61ms with 6 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.shared.ApiFailureHandlerSpec | 6✅ | 61ms |
✅ io.myfinbox.shared.ApiFailureHandlerSpec
✅ should throw NullPointerException when null failure
✅ should get conflict API response when conflict failure
✅ should get not found API response when not fount failure
✅ should get forbidden API response when action not allowed
✅ should get unprocessable entity API response when validation failure
✅ should throw IllegalArgumentException when not failure handler
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.spendingplan.adapter.messaging.ExpenseEventsListenerSpec.xml
4 tests were completed in 3s with 4 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.spendingplan.adapter.messaging.ExpenseEventsListenerSpec | 4✅ | 3s |
✅ io.myfinbox.spendingplan.adapter.messaging.ExpenseEventsListenerSpec
✅ should record received expense created event
✅ should record received expense updated event
✅ should record received expense updated event when category changed
✅ should record received expense deleted event when category
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.spendingplan.adapter.web.JarControllerSpec.xml
5 tests were completed in 2s with 5 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.spendingplan.adapter.web.JarControllerSpec | 5✅ | 2s |
✅ io.myfinbox.spendingplan.adapter.web.JarControllerSpec
✅ should create a new jar for an existing spending plan
✅ should fail creation when request has validation failures
✅ should fail creation when request resource jar percentage is greater than allowed
✅ should modify provided category list
✅ should fail to modify when plan jar not found
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.spendingplan.adapter.web.PlanControllerSpec.xml
6 tests were completed in 3s with 6 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.spendingplan.adapter.web.PlanControllerSpec | 6✅ | 3s |
✅ io.myfinbox.spendingplan.adapter.web.PlanControllerSpec
✅ should successfully create a new spending plan
✅ should fail creation when request has validation failures
✅ should create a new classic spending plan
✅ should fail classic plan creation when request has validation failures
✅ should update an existing spending plan
✅ should fail updating when request has validation failures
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.spendingplan.application.AddOrRemoveJarCategoryServiceSpec.xml
9 tests were completed in 42ms with 9 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.spendingplan.application.AddOrRemoveJarCategoryServiceSpec | 9✅ | 42ms |
✅ io.myfinbox.spendingplan.application.AddOrRemoveJarCategoryServiceSpec
✅ should fail modify categories to jar when invalid categories [categories: null, failMessage: At least one category must be provided., #0]
✅ should fail modify categories to jar when invalid categories [categories: [], failMessage: At least one category must be provided., #1]
✅ should fail modify categories to jar when invalid categories [categories: [[categoryId:null, toAdd:true]], failMessage: Null categoryId not allowed., #2]
✅ should fail modify categories to jar when invalid categories [categories: [[categoryId:e2709aa2-7907-4f78-98b6-0f36a0c1b5ca, toAdd:true], [categoryId:e2709aa2-7907-4f78-98b6-0f36a0c1b5ca, toAdd:true]], failMessage: Duplicate category ids provided., #3]
✅ should fail modify categories to jar when invalid categories
✅ should fail modify categories to jar when null plan ID
✅ should fail modify categories to jar when null jar ID
✅ should fail modify categories to jar when plan jar not found
✅ should modify categories to plan jar successfully
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.spendingplan.application.ClassicPlanBuilderServiceSpec.xml
3 tests were completed in 38ms with 3 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.spendingplan.application.ClassicPlanBuilderServiceSpec | 3✅ | 38ms |
✅ io.myfinbox.spendingplan.application.ClassicPlanBuilderServiceSpec
✅ should fail classic plan creation when plan validation failure
✅ should fail classic plan creation when jar validation failure
✅ should create a classic plan creation successfully
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.spendingplan.application.CreateJarServiceSpec.xml
14 tests were completed in 36ms with 14 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.spendingplan.application.CreateJarServiceSpec | 14✅ | 36ms |
✅ io.myfinbox.spendingplan.application.CreateJarServiceSpec
✅ should fail jar creation when name is invalid [jar: null, failMessage: Name cannot be empty., #0]
✅ should fail jar creation when name is invalid [jar: , failMessage: Name cannot be empty., #1]
✅ should fail jar creation when name is invalid [jar: , failMessage: Name cannot be empty., #2]
✅ should fail jar creation when name is invalid [jar: j6QrzhRDCIZp8sQY99USF2Ap3UqrpbDMvBGIdMb7SKkgRh44fRvNRzTuL6U9csbtfQd9V0SyaIX8v8eoy9IzMXXtQtQ00Tt9cB4PSFRdfSEF4FAuqhmDQ62Pj1iWDVzchbV5qQZLUUyPdtZHvBsd4LkOqwIJVldoJxyjDR56Np5tG9JpPLQjUcrISA1wJq0EBD6DVxK87lycpLsB661Pa07ij0ZBk30SoEijXxy0pArE0tcsouk3kgILJj5DRp5v, failMessage: Name length cannot exceed 255 characters., #3]
✅ should fail jar creation when name is invalid
✅ should fail jar creation when percentage is invalid [percentage: null, failMessage: Percentage cannot be null., #0]
✅ should fail jar creation when percentage is invalid [percentage: 0, failMessage: Percentage must be between 1 and 100., #1]
✅ should fail jar creation when percentage is invalid [percentage: -1, failMessage: Percentage must be between 1 and 100., #2]
✅ should fail jar creation when percentage is invalid [percentage: 101, failMessage: Percentage must be between 1 and 100., #3]
✅ should fail jar creation when percentage is invalid
✅ should fail jar creation when planId is null
✅ should fail jar creation when plan not found
✅ should fail plan creation when jar name for provided name already exists
✅ should create a new jar successfully
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.spendingplan.application.CreatePlanServiceSpec.xml
17 tests were completed in 34ms with 17 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.spendingplan.application.CreatePlanServiceSpec | 17✅ | 34ms |
✅ io.myfinbox.spendingplan.application.CreatePlanServiceSpec
✅ should fail plan creation when accountId is null
✅ should fail plan creation when name is invalid [planName: null, failMessage: Name cannot be empty., #0]
✅ should fail plan creation when name is invalid [planName: , failMessage: Name cannot be empty., #1]
✅ should fail plan creation when name is invalid [planName: , failMessage: Name cannot be empty., #2]
✅ should fail plan creation when name is invalid [planName: 5YzzLwydxouVw2wuoYKdPj56lDPsmdNAoeBPwZXae0rODCfvA7CAXtENFBUeDo0kneSYmvIv5gMngIDAaAVc1Td1f6RDx26WGmOA424U9XTcPcQjgwMj5d9w5mAYplzfGxKFP4eiWvqQfFobN0Ne4MVvsI3XippaPBcoWQ0uEnEPOKRfqLEC2EnwPAZCp9jbxql4xpX8QcmJq7DF5SAsMNjKaGWZvKJqITESosD7XMCucuZd0jgsNO2BTMk2SNtm, failMessage: Name length cannot exceed 255 characters., #3]
✅ should fail plan creation when name is invalid
✅ should fail plan creation when amount is invalid [value: null, failMessage: Amount cannot be null., #0]
✅ should fail plan creation when amount is invalid [value: 0.0, failMessage: Amount must be a positive value., #1]
✅ should fail plan creation when amount is invalid [value: -25.56, failMessage: Amount must be a positive value., #2]
✅ should fail plan creation when amount is invalid
✅ should fail plan creation when currencyCode is invalid [currencyCode: null, failMessage: CurrencyCode cannot be null., #0]
✅ should fail plan creation when currencyCode is invalid [currencyCode: , failMessage: CurrencyCode is not valid., #1]
✅ should fail plan creation when currencyCode is invalid [currencyCode: US, failMessage: CurrencyCode is not valid., #2]
✅ should fail plan creation when currencyCode is invalid [currencyCode: MDLA, failMessage: CurrencyCode is not valid., #3]
✅ should fail plan creation when currencyCode is invalid
✅ should fail plan creation when plan name already exit
✅ should create a new plan
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.spendingplan.application.ExpenseRecordTrackerServiceSpec.xml
8 tests were completed in 124ms with 8 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.spendingplan.application.ExpenseRecordTrackerServiceSpec | 8✅ | 124ms |
✅ io.myfinbox.spendingplan.application.ExpenseRecordTrackerServiceSpec
✅ should retrieve empty records when no category is tracked for a newly created expense record
✅ should create two expense records when category is tracked
✅ should return empty records when updating an expense with no existing records
✅ should update two expense records when category is tracked
✅ should create two new expense records when category is changed, with each record linked to the new category
✅ should create one new expense record when category is changed, linked to the new category
✅ should return empty records when attempting to delete a non-existent expense
✅ should delete one record when deleting an existing expense
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.spendingplan.application.UpdatePlanServiceSpec.xml
20 tests were completed in 56ms with 20 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.spendingplan.application.UpdatePlanServiceSpec | 20✅ | 56ms |
✅ io.myfinbox.spendingplan.application.UpdatePlanServiceSpec
✅ should fail plan updating when accountId is null
✅ should fail plan updating when name is invalid [planName: null, failMessage: Name cannot be empty., #0]
✅ should fail plan updating when name is invalid [planName: , failMessage: Name cannot be empty., #1]
✅ should fail plan updating when name is invalid [planName: , failMessage: Name cannot be empty., #2]
✅ should fail plan updating when name is invalid [planName: 06zMX7GcMNkfod1qJtlUB1SCQ4Z7fMEix2Yigr65hqXm6aF9QdCUS9J56q19tTAXjIzhtiZbs7JFqSZ5jplvTqDJEckWNloqY7qaW1GJ3vQRQYakPRvArtNllPnB6m8IzMhPAhAbrv2uMm1bw2en9XWrCobDHqfRaPTsiWBrhLRFLvuZ7ZBFsMUjGqcsTFfOBHcCvFJKMczRX4oPcdGhLeoR37w8BmBrqosQZOsDxGxgXAQGxBZrVoUyNu1pGTAK, failMessage: Name length cannot exceed 255 characters., #3]
✅ should fail plan updating when name is invalid
✅ should fail plan updating when amount is invalid [value: null, failMessage: Amount cannot be null., #0]
✅ should fail plan updating when amount is invalid [value: 0.0, failMessage: Amount must be a positive value., #1]
✅ should fail plan updating when amount is invalid [value: -25.56, failMessage: Amount must be a positive value., #2]
✅ should fail plan updating when amount is invalid
✅ should fail plan updating when currency code is invalid [currencyCode: null, failMessage: CurrencyCode cannot be null., #0]
✅ should fail plan updating when currency code is invalid [currencyCode: , failMessage: CurrencyCode is not valid., #1]
✅ should fail plan updating when currency code is invalid [currencyCode: US, failMessage: CurrencyCode is not valid., #2]
✅ should fail plan updating when currency code is invalid [currencyCode: MDLA, failMessage: CurrencyCode is not valid., #3]
✅ should fail plan updating when currency code is invalid
✅ should fail plan update when plan id is null
✅ should fail plan update when plan not found
✅ should skip update when plan not changed
✅ should fail plan update when plan name already exists
✅ should update plan successfully
Loading