Project

General

Profile

Actions

Feature #6549

closed

Core tests should be disable-able from plugins

Added by Greg Sutcliffe almost 10 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Plugin integration
Target version:
Difficulty:
medium
Triaged:
Fixed in Releases:
Found in Releases:

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


Related issues 1 (0 open1 closed)

Related to Foreman - Bug #11025: Test runner isn't run when using the Jenkins test tasksClosedEric Helms07/06/2015Actions
Actions #1

Updated by Greg Sutcliffe almost 10 years ago

  • Status changed from Assigned to Ready For Testing
Actions #2

Updated by The Foreman Bot almost 10 years ago

  • Pull request https://github.com/theforeman/foreman/pull/1576 added
Actions #3

Updated by Anonymous almost 10 years ago

  • Target version changed from 1.8.0 to 1.7.5
Actions #4

Updated by Anonymous almost 10 years ago

  • Target version changed from 1.7.5 to 1.7.4
Actions #5

Updated by Anonymous almost 10 years ago

  • Target version changed from 1.7.4 to 1.7.3
Actions #6

Updated by Dominic Cleal over 9 years ago

  • Translation missing: en.field_release set to 21
Actions #7

Updated by Greg Sutcliffe over 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #8

Updated by Dominic Cleal almost 9 years ago

  • Related to Bug #11025: Test runner isn't run when using the Jenkins test tasks added
Actions

Also available in: Atom PDF