When creating decoders it is very useful to be able to first test decoders before creating any matching rules.

[frankeros]

When creating decoders it is very useful to be able to first test decoders before creating any matching rules.
Currently testing a log that matches a decoder without matching a rule will again return the No result found message.
For example:

Apr 28 13:43:51 localhost local_decoder_example: test

Should result in:

**Phase 1: Completed pre-decoding.
        full event: 'Apr 28 13:43:51 localhost local_decoder_example: test'
        timestamp: 'Apr 28 13:43:51'
        hostname: 'localhost'
        program_name: 'local_decoder_example'

**Phase 2: Completed decoding.
        name: 'local_decoder_example'

Instead it returns:

No result found for:  Apr 28 13:43:51 localhost local_decoder_example: test 

This is testing with the app compiled at 87fba01

Originally posted by @jctello in #3193 (comment)

[sortiz1191]

Tested logtest for rulesets and decoders.

Check if the data is from a ruleset or from a decoder and show data depending on the case.

[branchnetconsulting]

This continues to be broken as of 4.2.4. Also, the issue is broader than just affecting decoder tests. If you create a custom top level parent rule and then use the webui logtest feature to test it with a log sample, you will also only see "No result found..." It appears presently when the WebUI calls wazuh-logtest that unless the results include "**Alert to be generated.", the only thing that will be displayed in the web output will be "No result found...". Please remove that check and simply let the full output of wazuh-logtest be conveyed to the web results window.