| Summary: | ASTERISK-24203: Sorcery: Allow for tests to temporarily select a sorcery wizard | ||
| Reporter: | Mark Michelson (mmichelson) | Labels: | |
| Date Opened: | 2014-08-11 12:54:35 | Date Closed: | |
| Priority: | Minor | Regression? | No |
| Status: | Open/New | Components: | Core/Sorcery Tests/NewFeature |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | 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. | ||
| Comments: | |||