Anuket Project

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Dovetail PlugFest activities and desired outcome:

1. Test toolchain and work flow validation

Pre-requisite:

  • a dovetail client software (alpha version) available prior to the start of the PlugFest
  • a LF-hosted web server / DB available for testing purpose
  • A draft of test strategy document: at least the tester guide sections

Desired outcome of the validation

  • confirmation of the work flow's validity, or JIRA tickets to fix issues
  • confirmation of dovetail client software feature completeness, or JIRA tickets to enhance or fix issues
  • any feedback to web server / DB and feature enhancements

2. Validating draft test suite and test toolchain on a varieties of hardware and software stack combinations (scenarios)

Pre-requiste:

  • Same as above

Desired outcome

  • Testing dovetail on one or more hardware (inc. network) configurations
  • Testing dovetail on more than one scenarios/installers (details in the table below)
  • If vendor software available, test dovetail on vendor distributions. (this can also happen in private lab environment remotely)

3. Review of the documentation to be released with cvp

The test user guide: How to prepare a system, run the test suite, and validate the results

4. Review of test areas

Possible areas include sdn controllers, ha, ipv6, sdnvpn, ...

-------------

PlugFest testing proposal for Dovetail:

hardwarecloudOSinstaller dovetail test time
HuaweiDanube/windriver?compass?apex? 4/25
IntelDanube/windriver?compass?apex?  
NokiaDanube/windriver?compass?apex? 4/24
Lenovo Danube/windriver?compass?apex? yes, time(TBD)
AdvantechDanube/windriver?compass?apex?  
OrangeDanube/windriver?compass?apex?  
NECDanube/windriver?compass?apex?  
hardware?windriver  yes

 

HackFest dovetail meeting sessions: 

Danube Plugfest/Hackfest planning page

 

Compliance Testing - performance

1 hour

Trevor Cooper

Unknown User (hongbotian)

CVP for E release will include "performance" compliance tests ... lets focus on what this means and discuss requirements/methods/tools/etc.
review test area and test cases?  

 

 

 

  • No labels