Functional Testing (Top, Bottom & Changed ) for microversions
As Nova have around 12 microversion which keep increasing, it is imp to cover their testing to make sure each microversion is behaving as expected.
Currently each microversion has their Unit and Functional tests to verify the expected behavior of that version.
But there should be more test coverage for each microversion like below.
- Tests against Top(which will be that microverion)
- Test against Bottom (2.1) and make sure changes done in that microversion are not reflecting with 2.1 version.
- Test against Changed (immediate previous version) and make sure changes done in that microversion are not reflecting with previous version.
Blueprint information
- Status:
- Not started
- Approver:
- John Garbutt
- Priority:
- Low
- Drafter:
- Ghanshyam Mann
- Direction:
- Needs approval
- Assignee:
- Ghanshyam Mann
- Definition:
- Pending Approval
- Series goal:
- None
- Implementation:
-
Not started
- Milestone target:
-
next
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
marking this as low priority to make it clear that the doc work is more important right now. --johnthetubaguy 20151110
Sorry, we have now hit the Non-Priority Feature Freeze for Mitaka. For more details please see: http://
--johnthetubaguy 2016.01.30
Providing some example scenarios would be nice to help clarify this, e.g. I'm modifying an existing API for a new 2.40 microversion, this tests 2.40 and 2.39. And if I'm adding a new API in 2.45, and it runs 2.44 it asserts there is a 404 since the API didn't exist before 2.45. -- mriedem 20170224
Deferring to Queens since there are no changes available for this in Pike so I'd like to focus the rest of our review efforts on things that have a chance of landing in Pike. -- 20170608
