matchers | Hamcrest 1.3 Utility Matchers

If an exception is thrown inside the Given or When block, the test initialisation fails. Here is the output if I run that one test only:

It seems that exceptions are only handled inside the Then blocks.

This means that everything that can throw an exception should go into Then blocks, which in turn means that setup and action cannot be shared between the tests:

TL;DR You can't extend expect because of the type declarations they use.

You should open an issue for that documentation.

Looking at the type declarations, we see that Expect is a type alias and not an interface...

Which means we can't augment this type...

If they changed it to an interface then we could augment the module and add our extensions.

So for that, you also might want to open an issue or a pull request to fix it (fixing it is literally changing one line or two).

Found the answer here -> https://github.com/storybookjs/storybook/issues/15336

The solution is simply to add the following to .storybook\main.js

I believe it is because you forget to mock the method PunishmentValidator#validatePunishmentName("mute") to return true such that the method that you stub on PunishmentService is never invoked because by default if you do not stub a method , it will return false (see this).

Also it is a known behaviour that @MockBean is configured as lenient stubbing which will not reported error (i.e. throw UnnecessaryStubbingException) if you stub a method but it actually does not get executed.

So change the following should fix your problem :

It seems to me that you forgot to add all the modules of this class. Try to update the spec/controllers/api/v1/categories_controller_spec.rb too:

First of all, the message about DidYouMean is a deprecation warning not an error, it doesn't break your app. It means that usage of DidYouMean::SPELL_CHECKERS is deprecated and will be removed in a future version of ruby. In this case in Ruby 3.3. You shouldn't worry about it until you use versions that are lower than 3.3. It's not your code that triggers the warning. It comes from a gem named Thor. The issue was solved in thor version 1.2.0. You can update the gem by calling bundle update thor.

The actual error comes from the bootsnap gem:

The "\\\\d{4}" string literal defines a \\d{4} regex that matches a \dddd string (a backslash and then four d chars). You try to access Group 4, but there is no capturing group defined in your regex. Besides, you can't access match groups before actually running the matcher with Matcher#find or Matcher#matches.

You can use

The Junit4 is available because of Testcontainer dependency. Testcontainers have a dependency on Junit4 and have it available by default. You might also encounter the following issue in few cases:

• IDE's detects the test cases written in Junit4 format but in sometime in case you make the test classes and methods package-private, they don't detect it.

I am not sure if they would be removing it in further releases but they do have Junit5 support which should resolve the issue

• https://www.testcontainers.org/test_framework_integration/junit_5/

Not sure how your log lines look exactly, but I think you don't need to extract the labels out (by using | json

This is a pretty useful article on how to write queries. how-to-create-fast-queries-with-lokis-logql-to-filter-terabytes-of-logs-in-seconds You can also make use of the new Pattern parser instead of the regex if you want to make the query more readable.

So without really knowing how your log lines look, I think this should work well: