View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001102 | Compliance Test Tool (CTT) Unified Architecture | public | 2010-04-20 04:30 | 2012-12-11 15:21 | |
Reporter | Randy Armstrong | Assigned To | Randy Armstrong | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Summary | 0001102: Test 6.1.2 Test 3 - Expects overflow when Queue Size == 1 | ||||
Description | QueueSize == 1 and QueueSize == 0 both mean no queuing according to the specification so the overflow bit will never be set. Use a queue size of at least 2. | ||||
Tags | No tags attached. | ||||
Files Affected | |||||
related to | 0001120 | closed | Matthias Damm | 10000-004: Services | QueueSize and Overflow bit clarification |
|
I think you have a very valid point here and your comments make perfect logical sense. I have reviewed part 4, but I do not see anything that states the overflow to be used when the queuesize is >1. I am thinking that the spec should be revised to match your suggestion. At the same time, to revise the test-case to then verify that the overflow bit is NOT set. However, I would be more comfortable making the change to the test-script only once the spec is changed. Thoughts? |
|
I have revised the script to verify that the overflow bit is not set. A spec clarification has been requested in Mantis issue 1120. |
Date Modified | Username | Field | Change |
---|---|---|---|
2010-04-20 04:30 | Randy Armstrong | New Issue | |
2010-04-20 15:34 |
|
Status | new => assigned |
2010-04-20 15:34 |
|
Assigned To | => Nathan Pocock |
2010-04-21 16:16 |
|
Note Added: 0001688 | |
2010-04-21 16:16 |
|
Assigned To | Nathan Pocock => Randy Armstrong |
2010-04-21 16:16 |
|
Status | assigned => feedback |
2010-04-21 16:38 |
|
Status | feedback => resolved |
2010-04-21 16:38 |
|
Resolution | open => fixed |
2010-04-21 16:38 |
|
Note Added: 0001690 | |
2010-04-21 16:38 |
|
Relationship added | related to 0001120 |
2012-12-11 15:21 |
|
Status | resolved => closed |
2014-08-28 14:03 |
|
Category | Implementation Bug => (No Category) |