[CONTROLLER-567] Analyze existing test suites and testing options Created: 20/Jun/14  Updated: 25/Jul/23  Due: 25/Jul/14  Resolved: 19/Aug/14

Status: Resolved
Project: controller
Component/s: mdsal
Affects Version/s: None
Fix Version/s: None

Type: Improvement
Reporter: Viera Zelcamova Assignee: Tony Tkacik
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Blocks
blocks CONTROLLER-495 Milestone: Design MD-SAL Regression a... Resolved
blocks CONTROLLER-569 Design test-cases and scenarios Resolved

 Comments   
Comment by Tony Tkacik [ 25/Jul/14 ]

Currently for Testing we are using several approaches which are:

    1. MD-SAL Based suided
  • MD-SAL Test deployer - mostly for integration testing and legacy API support, where fully working MD-SAL is deployed
  • Set of Abstract*Test used for unit testing of MD-SAL, may be used for unit testing of client code
  • AbstractSchemaAwareTest - test which loads yang schema from classpath and instantiates runtime codecs
  • AbstractDataBrokerTest - test which instantiates binding broker, dom broker and datastore
  • AbstractChangeListenerTest - variation of DataBroker test which has possibility for simple data change event testing

All these are exported as test-jar for sal-binding-broker

Config subsystem based test-suite: mostly u

Comment by Tony Tkacik [ 28/Jul/14 ]

https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Testing#Testing_Tools

Generated at Wed Feb 07 19:53:21 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.