[asterisk-bugs] [JIRA] (ASTERISK-24203) Sorcery: Allow for tests to temporarily select a sorcery wizard

[Mark Michelson (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-24203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Michelson moved AFS-147 to ASTERISK-24203:
-----------------------------------------------

    Asterisk Issue Guidelines: Yes.
                     Security: None  (was: Digium Only)
                   Regression: No
                     Workflow: Subtask and Courtesy Workflow  (was: Software Planning Workflow)
                          Key: ASTERISK-24203  (was: AFS-147)
                      Project: Asterisk  (was: Asterisk for SwitchVox (Internal))

> Sorcery: Allow for tests to temporarily select a sorcery wizard
> ---------------------------------------------------------------
>
>                 Key: ASTERISK-24203
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24203
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>            Reporter: Mark Michelson
>            Assignee: Mark Michelson
>
> Unit tests in Asterisk often tests objects that are managed by sorcery. If the sorcery object, by default, uses res_sorcery_config as its wizard, then the unit test is dependent on having a specific configuration file with the object configuration in it. The way that sorcery has worked around this previously is to have a sorcery.conf file that overrides the default wizard for the sorcery object type with one that allows for creation of the object in-place.
> A better solution would be for sorcery to have an API call, presumably only when TEST_FRAMEWORK is enabled, that allows for an object type to change its default wizard temporarily. A similar API call could be added to restore the default wizard when the test has completed.



--
This message was sent by Atlassian JIRA
(v6.2#6252)