Actions
Feature #6549
closedCore tests should be disable-able from plugins
Description
Sometime plugins need to modify tests. Consider this scenario:
Core (psuedocode):
test "a thing" do
assert Hosts page should have one menu entry containing "Hosts"
end
This will pass, as we have just "All Hosts" by default. Now add the Discovery plugin, and this test will fail, as now we have "All Hosts" and "Discovered Hosts"
In general, we need a way for plugins to tell core that certain tests no longer make sense while the plugin is present - we assume the plugin itself will contain tests for the new/modified functionality
Updated by Greg Sutcliffe over 10 years ago
- Status changed from Assigned to Ready For Testing
Updated by The Foreman Bot over 10 years ago
- Pull request https://github.com/theforeman/foreman/pull/1576 added
Updated by Anonymous over 10 years ago
- Target version changed from 1.8.0 to 1.7.5
Updated by Anonymous about 10 years ago
- Target version changed from 1.7.5 to 1.7.4
Updated by Anonymous about 10 years ago
- Target version changed from 1.7.4 to 1.7.3
Updated by Dominic Cleal about 10 years ago
- Translation missing: en.field_release set to 21
Updated by Greg Sutcliffe about 10 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset c4741504ec7d4bae511c02aa1f708bb29f80057b.
Updated by Dominic Cleal over 9 years ago
- Related to Bug #11025: Test runner isn't run when using the Jenkins test tasks added
Actions