Bug 102484 – "Test Not Available" page gives misleading impression

Bug 102484 - "Test Not Available" page gives misleading impression

Summary:	"Test Not Available" page gives misleading impression

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Academy
Classification:	Retired
Component:	Web Application (Show other bugs)
Sub Component:
Version:	9
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Luke Meyer
QA Contact:	Bowe Strickland
Docs Contact:

URL:	https://academy.redhat.com/student/te...
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-08-15 16:15 EDT by Bowe Strickland
Modified:	2005-10-31 17:00 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-11-02 17:36:47 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Bowe Strickland 2003-08-15 16:15:08 EDT

when starting one test, and attempting to view another (because of bug nubmer
102483), the following message occurs:

>> This test is not currently available. It is currently scheduled during the
time >> period listed below.
>> Start time: Fri 8-Aug-2003 02:23pm
>> End time: Mon 8-Sep-2003 02:23pm

while accurate, it gives the impression that access was blocked because the time
was wrong, when in actuallity its blocked because another, concurrently enabled,
test has been started.  message should reflect that possibility.

Comment 1 Luke Meyer 2003-08-19 16:30:38 EDT

typically, the student will only get to this page via a link in the "blocked
tests" section -- it's only due to the other bug that it is confusing.  however
i agree that it might be a good idea eventually to explain on this page why the
test is not currently enabled.

Note You need to log in before you can comment on or make changes to this bug.