Atlassian JIRA
| Log4JHackery | We want to change our Log4j settings during func tests runs to get rid of a lot of the repetitive cruft that makes it hard to see real failures. |
| BarrierBackdoor | Backdoor for manipulating barriers remotely. |
| EntityEngineBackdoor | Use this backdoor to manipulate User Profiles as part of setup for tests. |
| FieldConfigurationBackdoorExt | A backdoor for manipulating field configurations. |
| FilterSubscriptionBackdoor | |
| IndexingBackdoor | Backdoor for starting/stopping/querying indexing. |
| IssueTypeScreenSchemesBackdoor | Use this backdoor to manipulate Issue Type Screen Schemes as part of setup for tests. |
| JiraConcurrentRequestsInfo | Provide some info to the selenium tests about the number of concurrent requests This resource has the advantage that it doesn't trigger the loading of other resources (e.g. |
| Log4JHackeryImpl | |
| ManagedConfigurationBackdoor | Controls managed configuration |
| PermissionsBackdoorExt | Extended PermissionsBackdoor. |
| QuickAdditionsBackdoor | |
| ScreensBackdoorExt | Extended ScreensBackdoor. |
| TestRunnerBackdoor | This is a backdoor for executing integration tests on the server remotely (via a Web Func Test). |
| TestRunnerBackdoor.TestResultResponse | |
| UserProfileBackdoor | Use this backdoor to manipulate User Profiles as part of setup for tests. |
| WorkflowSchemeProjectBackdoorExt | Extended WorkflowSchemeProjectBackdoor. |