Feature/ADF-1695/Show multiple preview buttons

[jsconan]

Related to: https://oat-sa.atlassian.net/browse/ADF-1695

Summary

Add the possibility of having more than one test previewer.

Details

It supports multiple preview buttons from the test's property page.

This is made thanks to a configuration applied in config/tao/client_lib_config_registry.conf.php, and a change applied to the structures.xml file.

• structures.xml
  Each button must be declared with an identifier starting with test-preview. The first button must be test-preview, the second test-preview-1, etc. The suffix number refers to a position in the configuration (see client_lib_config_registry.conf.php).
  Example:

    <structure id="tests" name="Tests" level="1" group="main">
        <sections>
            <section id="manage_tests" name="Manage tests" url="/taoTests/Tests/index">
                <actions allowClassActions="true">
                    <action id="test-preview" name="Preview" url="/taoTests/Tests/index" context="instance" group="content" binding="testPreview">
                        <icon id="icon-preview"/>
                    </action>
                    <action id="test-preview-1" name="Preview (legacy)" url="/taoTests/Tests/index" context="instance" group="content" binding="testPreview">
                        <icon id="icon-preview"/>
                    </action>
                </actions>
            </section>
        </sections>
    </structure>

• client_lib_config_registry.conf.php
  The configuration can be extended with a list of possible providers, aside from the default one. This is done in config/tao/client_lib_config_registry.conf.php.
  Example:

        'taoTests/controller/tests/action' => array(
            'provider' => 'qtiTestNUI',
            'providers' => array(
                array(
                    'id' => 'qtiTestNUI',
                    'label' => 'Preview'
                ),
                array(
                    'id' => 'qtiTest',
                    'label' => 'Preview (legacy)'
                )
            )
        ),

How to test

• checkout the branch: git checkout -t origin/feature/ADF-1695/multiple-preview-buttons
• also checkout the branches from the companion PR
• make sure to have set the appropriate configuration (check the details in the ticket)

[github-actions]

Front-end summary Node 18

💯 Total	✅ Passed	⏭️ Skipped	❌ Failed
0	0	0	0

[gabrielfs7]

I see these logics are repeated in the item extension too. I've left some comments there that may apply here too (like, if the fixed 10 may become a problem later).

Would it be possible to have this duplicated logic centralized in some place instead?

[jsconan]

Indeed, not the best. I've updated it with a constant instead.

[github-actions]

Version

Target Version	16.2.0
Last version	16.1.4

There are 0 BREAKING CHANGE, 2 features, 0 fix

[shaveko]

Looks fine

Looks fine

• New code is covered by tests (if applicable)
• Tests are running successfully (old and new ones) on my local machine (if applicable)
• New code is respecting code style rules
• New code is respecting best practices
• New code is not subject to concurrency issues (if applicable)
• Feature is working correctly on my local machine (if applicable)
• Acceptance criteria are respected
• Pull request title and description are meaningful

[gabrielfs7]

LGTM

• New code is covered by tests (if applicable)
• Tests are running successfully (old and new ones) on my local machine (if applicable)
• New code is respecting code style rules
• New code is respecting best practices
• New code is not subject to concurrency issues (if applicable)
• Feature is working correctly on my local machine (if applicable)
• Acceptance criteria are respected
• Pull request title and description are meaningful