Enable account locale resolving and add account preference #93
GitHub Actions / Test Reports
succeeded
Aug 4, 2024 in 0s
295 passed, 0 failed and 0 skipped
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.account.adapter.web.AccountControllerSpec.xml
2 tests were completed in 18s with 2 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.account.adapter.web.AccountControllerSpec | 2✅ | 18s |
✅ 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
✅ /home/runner/work/myfinbox/myfinbox/server/target/failsafe-reports/TEST-io.myfinbox.account.application.CreateAccountServiceSpec.xml
33 tests were completed in 932ms with 33 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.account.application.CreateAccountServiceSpec | 33✅ | 932ms |
✅ 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 2s with 1 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.expense.adapter.messaging.AccountEventsListenerSpec | 1✅ | 2s |
✅ 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 112ms with 6 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.expense.adapter.web.ExpenseCategoryControllerSpec | 6✅ | 112ms |
✅ 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 2s with 6 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.expense.adapter.web.ExpenseControllerSpec | 6✅ | 2s |
✅ 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 67ms with 18 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.expense.application.CreateExpenseServiceSpec | 18✅ | 67ms |
✅ 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 74ms with 25 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.expense.application.DefaultCategoryServiceSpec | 25✅ | 74ms |
✅ 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: 2mQKXmjC9ev7tCcZMiYTdEx18NJB6YFlm1XUoXgWtxXS9DJmBknrDZnfMbBp29D4MjDQa2HQpefCeMnm8VUNEmbEM7V31yonHtejvSFvzWakG8N95GtRQTEBvMVjhVc1gK1KmoURtDKUql1aKYEwgajuwueqcnfxehkoQ9cI2FL6cLu4ITDqNcgYWr71QVvaM0NILalQHWmSJiY8zDimMlGv6ahmL1sDWTXL8YRVZxiyn5jotAIKg6qs3rvXmKou, 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: 2MwCP47BniKKJGJDI0j8bsa5UOutA4LlteSqUDg5d9OvYMs4GsSWKYurGAN7lVrfVTjbUnnPsICEA21YLk9cZoKhEqZcadMm71B5WFiPz2yX1C2zqQPbOKTvVM0j33kWg0Kj2a1KXfwQYusE1Q1BFb2mcynfgB45rys6S9bczvWDwfZyS2IiACnqm6W9cyajHLMK3xM37GlkwCV0sDgrZaxy54ixio4wELnDspzAtL0rLjs5CeytPdloRpsMmj68, 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 10ms with 3 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.expense.application.DeleteExpenseServiceSpec | 3✅ | 10ms |
✅ 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 51ms with 20 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.expense.application.UpdateExpenseServiceSpec | 20✅ | 51ms |
✅ 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 3s with 1 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.income.adapter.messaging.AccountEventsListenerSpec | 1✅ | 3s |
✅ 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 3s with 6 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.income.adapter.web.IncomeControllerSpec | 6✅ | 3s |
✅ 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 223ms with 6 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.income.adapter.web.IncomeSourceControllerSpec | 6✅ | 223ms |
✅ 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 170ms with 18 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.income.application.CreateIncomeServiceSpec | 18✅ | 170ms |
✅ 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 227ms with 25 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.income.application.DefaultIncomeSourceServiceSpec | 25✅ | 227ms |
✅ 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: wJoiAbfvTIrj4f3GiQimJDCHJU3EbYW6qbIWkr2etvevHX4HhtnpEmRnaWbXz8FywhQDIiX3UDnpTWPqoRAS0oXyWzHbWSEPjb2m0b1eyDB6RHBIa0qQGDdaO21VkeNSEWiskWXNcZcXMuKHM4iunM1cIzbc5jxpV1k1ekyi1mYBvqlq2gHu2ULeijETyJvlQInVVfZyxOtQsapkctkyLcxEZAJtXdcf22hRTizhl4QjQtetJ6LgSPS5Y8KWcl25, 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: TwRHFtzfY0xvU9J2UsEvCErt75feLPG42aAGDdJxFlZD4q73hpwD9VXAs9uu0d6l3Jjjgk179cddZxcgJTWGOy1OTFV0YZipZv76gtiA1yNx3rvdVsfpisVfZ38906x6RjxWiNUyPwxOjoRScmQpIPVj7yLPxXttDItIEqq74hbNnIhhr2FEThoSbDyMpUHvv9xOG0X5FjUgvK4CccxLljpHouQLLvcUspQHHmTTFTMMLyevOyGNLwNp9AB6DOBu, 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 12ms with 3 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.income.application.DeleteIncomeServiceSpec | 3✅ | 12ms |
✅ 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 56ms with 20 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.income.application.UpdateIncomeServiceSpec | 20✅ | 56ms |
✅ 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 5s with 2 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.ModularitySpec | 2✅ | 5s |
✅ 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 4s with 1 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.ServerApplicationSpec | 1✅ | 4s |
✅ 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 4s with 7 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.shared.ApiExceptionHandlerSpec | 7✅ | 4s |
✅ 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 135ms with 6 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.shared.ApiFailureHandlerSpec | 6✅ | 135ms |
✅ 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 3s with 5 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.spendingplan.adapter.web.JarControllerSpec | 5✅ | 3s |
✅ 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 2s with 6 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.spendingplan.adapter.web.PlanControllerSpec | 6✅ | 2s |
✅ 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 59ms with 9 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.spendingplan.application.AddOrRemoveJarCategoryServiceSpec | 9✅ | 59ms |
✅ 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 61ms with 3 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.spendingplan.application.ClassicPlanBuilderServiceSpec | 3✅ | 61ms |
✅ 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 33ms with 14 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.spendingplan.application.CreateJarServiceSpec | 14✅ | 33ms |
✅ 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: tzHCp0OY01uAIiBaa9KpEI53caUWZaRb1UizxnU49xfzogWCBKN1lELuf47uCQFPAHxjXeMoBkZFulGYHctfyTPkKsSqTvz8y7nTK7mqS8HtsnUEikf8yQkvXXpDuR3ol93pBUFLRSDSq28jmRKLdiAeTFXAPVLLezBYaAIrJcJhbNuRGWT57eR7MnKiqfxAeLN6UTDnBxjc4QSqxNM1begXeZpmvErRwfxSfdaD99ZixNNn6tXKgOxXwy4oB0JV, 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 41ms with 17 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.spendingplan.application.CreatePlanServiceSpec | 17✅ | 41ms |
✅ 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: 7cGV5rYDaXEaQJkZwvFh7vkZ6IsdImtKNCP87QrxeLZcD6Ixa7DuOwB92o3EETFAuJrIZCAp2hPtA5K9UQcMyxVH3nLsKoyyA9SoyP9rUc0YE7c5i8qL6aOJNMFLWnCc6pLwhkw4FAzS6iKWdoaosOh6hzpS6vrD8Jdc8LDDZSivLMqUexjAro6GXUDsvl2bcfAXEDk66ZrTqO2hujrc5swpXPZXa59JTHu5zJd4OU35DukHkzKVNa8HJrkC66Zl, 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 53ms with 8 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.spendingplan.application.ExpenseRecordTrackerServiceSpec | 8✅ | 53ms |
✅ 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 64ms with 20 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| io.myfinbox.spendingplan.application.UpdatePlanServiceSpec | 20✅ | 64ms |
✅ 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: 626pXZqPU7mMWnnlfEVPZuaN5Yq7ww56o85JO7PNlzK1X2sYnvnMVmg27vRWIQ3lRrklzJK1M3aCb5c4mfzUNV1CL998AXztHid49dGkfeOa3A5VdKU5EEGjcwluSVJfcvCocuOMTyT8HzW1Ylg954gUvZjlX23qMUQmEEB7kdGeRGd0RUp1gIjkQ8njIchc0bkMtRJdlEfnbY3pXaMoilGcTMf8Qs43jzaUvOgh80n7BzDKxHXo4kHWeutaow3F, 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