Hi Bart, The statement in task AppOperator of sysinv SB prefers adding tests for one method in each commit, while the etherpad shows "use a single commit for each Storyboard Task". Does it mean each test for each method in AppOperator class needs a task created in SB 2007082 respectively? What's the best practice of this operation? (or create tasks in a separate SB?) Mingyuan -----Original Message----- From: Zvonar, Bill <Bill.Zvonar@windriver.com> Sent: Friday, January 10, 2020 22:15 To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Test Hack-a-thon Etherpad... Hi folks - the etherpad for the Test Hack-a-thon is open at https://etherpad.openstack.org/p/stx-test-hackathon. More details to be added, but as discussed in the Community Call yesterday, we'll use this to keep track of who's working on what. Please indicate which areas/tasks you will work on in the list on the etherpad. Let's get hacking! Bill... _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss