openinfra/interop
Code Issues Proposed changes

Refactor json for coretests to include criteria information.

Browse Source 
This information is needed to build displays that include the
scores of specific tests.  We will need this for discussions related
to the scoring of tests in the future.

In order to add capabilities, we also needed to create a
top level hash.

Change-Id: I4ad213afca382ec4a401f0ffe2f4ac3c007ce967
This commit is contained in:
Rob Hirschfeld 2014-05-25 21:15:05 -05:00
parent a94fb84241
commit ec2fb5a3d6
1 changed files with 371 additions and 333 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

40
havana/coretests.json
View File

@ -1,4 +1,41 @@
{ "test_access_public_container_object_without_using_creds" : { "file" : "test_object_services.py" },
{ "criteria" : { "atomic" : { "Description" : "Capabilities is unique and cannot be built out of other must-pass capabilities",
"name" : "Atomic"
},
"clients" : { "Description" : "Candidates are widely used capabilities: Should be included if part of common libraries (Fog, Apache jclouds, etc)",
"name" : "Used by Clients"
},
"complete" : { "Description" : "Where the code being tested has a designated area of alternate implementation (extension framework) as per the Core Principles, there should be parity in capability tested across extension implementations. This also implies that the capability test is not configuration specific or locked to non-open technology.",
"name" : "Complete"
},
"core" : { "Description" : "A test that is a must-pass test should stay a must-pass test. This make makes core capabilities sticky release per release. Leaving Core is disruptive to the ecosystem",
"name" : "Core in Last Release"
},
"deployed" : { "Description" : "Candidates are widely deployed capabilities. We favor capabilities that are supported by multiple public cloud providers and private cloud products.",
"name" : "Widely Deployed"
},
"discover" : { "Description" : "Capability being tested is Service Discoverable (can be found in Keystone and via service introspection)",
"name" : "Discoverable"
},
"doc" : { "Description" : "Should be well documented, particularly the expected behavior. This can be a very subjective measure and we expect to refine this definition over time.",
"name" : "Documented"
},
"foundation" : { "Description" : "Test capabilities that are required by other must-pass tests and/or depended on by many other capabilities",
"name" : "Foundation"
},
"future" : { "Description" : "Should reflect future technical direction (from the project technical teams and the TC) and help manage deprecated capabilities.",
"name" : "Future Direction"
},
"proximity" : { "Description" : "Sometimes called a Test Cluster, selects for Capabilities that are related to Core Capabilities. This helps ensure that related capabilities are managed together.",
"name" : "Proximity"
},
"stable" : { "Description" : "Test is required stable for >2 releases because we don't want core capabilities that do not have dependable APIs.",
"name" : "Stable"
},
"tools" : { "Description" : "Candidates are widely used capabilities:Should be included if supported by common tools (RightScale, Scalr, CloudForms, ...)",
"name" : "Used by Tools"
}
},
"tests" : { "test_access_public_container_object_without_using_creds" : { "file" : "test_object_services.py" },
"test_access_public_object_with_another_user_creds" : { "file" : "test_object_services.py" },
"test_add_image_member" : { "file" : "v1/test_image_members.py" },
"test_add_member_with_non_existing_image" : { "file" : "v1/test_image_members.py" },
@ -331,4 +368,5 @@
"test_write_object_without_rights" : { "file" : "test_container_acl.py" },
"test_write_object_without_using_creds" : { "file" : "test_container_acl.py" },
"test_write_object_without_write_rights" : { "file" : "test_container_acl.py" }
}
}