View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002568Compliance Test Tool (CTT) Unified Architecture3 - Feature Requestpublic2013-08-20 20:292019-01-04 16:29
ReporterMatthias Damm Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityalways
Status assignedResolutionfixed 
Product Version1.02.334.200 
Target Version1.04 
Summary0002568: Revise FindServer test case for redundant servers
Description

Input from Part 4 Mantis issue (see related):
The CTT expects a server to return only a description of itself in test case 002.js in group "Discovery Find Servers Filter".

FindServers test must accept one entry for each server in the redundant set if the server supports non-transparent redundancy.

TagsNo tags attached.
Files Affected

Relationships

related to 0002360 closedMatthias Damm 10000-004: Services Inconsistency in behavior of FindServers service 

Activities

Nathan Pocock

2014-08-20 21:00

viewer   ~0005458

Hello Matthias,

The redundancy scenario definitely changes this test-case.

I think that this specific test may need to be "forked" such that:

  • test #A: does as it does now (no redundancy)
  • test #B: behaves per your suggestion(non-transparent redundancy)

In this case, the script will detect the type of server (redundant or not) and will then change its expectations accordingly. What do you think?

Matthias Damm

2014-08-21 15:59

reporter   ~0005459

Hi Nate

The existing test case must be changed to accept more then the own server if Non-Transparent Redundancy is active for the server.

In addition we need a new test case that checks if all servers in the redundant set are returned in FindServer if the server claims to support Non-Transparent Redundancy. This new test case is related to the according redundancy conformance unit.

Matthias

Nathan Pocock

2016-02-12 17:09

viewer   ~0006716

Fixed. Will be in the next release.
This case to be closed on external confirmation.

Paul Hunkar

2018-11-09 15:55

administrator   ~0009561

Review how the redundant case is handled (will need more cases for transparent, Non-transparent, network redundant and non-redundant)

Issue History

Date Modified Username Field Change
2013-08-20 20:29 Matthias Damm New Issue
2013-08-20 20:29 Matthias Damm Relationship added related to 0002360
2013-08-20 20:30 Matthias Damm Status new => assigned
2013-08-20 20:30 Matthias Damm Assigned To => Nathan Pocock
2014-08-20 21:00 Nathan Pocock Note Added: 0005458
2014-08-20 21:00 Nathan Pocock Assigned To Nathan Pocock => Matthias Damm
2014-08-20 21:00 Nathan Pocock Status assigned => feedback
2014-08-20 21:00 Nathan Pocock Target Version => 1.02.335
2014-08-21 15:59 Matthias Damm Note Added: 0005459
2014-08-21 15:59 Matthias Damm Status feedback => assigned
2014-08-21 15:59 Matthias Damm Assigned To Matthias Damm => Nathan Pocock
2014-08-21 15:59 Matthias Damm Status assigned => new
2014-08-28 14:03 Nathan Pocock Category Implementation Bug => (No Category)
2014-08-28 14:12 Nathan Pocock Status new => assigned
2014-08-28 14:12 Nathan Pocock Category (No Category) => IOP Problem
2014-08-28 14:12 Nathan Pocock Product Version => 1.02.334.200
2016-02-12 17:09 Nathan Pocock Note Added: 0006716
2016-02-12 17:09 Nathan Pocock Status assigned => resolved
2016-02-12 17:09 Nathan Pocock Resolution open => fixed
2018-11-09 15:54 Paul Hunkar Assigned To Nathan Pocock => Alexander Allmendinger
2018-11-09 15:54 Paul Hunkar Status resolved => assigned
2018-11-09 15:55 Paul Hunkar Note Added: 0009561
2019-01-04 16:29 Paul Hunkar Category IOP Problem => Feature Request
2019-01-04 16:29 Paul Hunkar Target Version 1.02.335 => 1.04
2019-01-28 14:14 Paul Hunkar Category Feature Request => 3 - Feature Request