Meeting minutes - 12/11 Attendees: Bruce, Elio, Jose, Maria, Abraham, JC, Numan, JP, Ada, David, Cristopher * Test case template - Numan - Numan presented a proposal for a document for writing test cases - Priority - who will define the priority of the test case? The one writing the test case? Suggestions is to define a set of rules for helping on defining the right priority - Question: who will be responsible for maintaining the test management tool? We need to define a role for taking ownership of this task - Feature field: use the storyboard number - Steps: use descriptive steps - Expected results: include check points - Could be written between developer and testing teams - The template is for unit test and functional test - Working on developing tests for new features is along done - Ada to upload the documents to the wiki * Proposal for an unified test suite - Jose - Jose presented robot framework Open source project supports CLI and GUI tests No extra packages required into the entity being tested Can execute native (Stx specific tests) or external suites (like tempest), bash scripting could also be run into Robot Robot uses tags for building test plans: regression, feature, etc It generates reports automatically - Jose to send the presentation to the mailing list for getting feedback from the community - Numan to contribute with the disadvantages they found when evaluating Robot * Pushed for next week: - Sanity testing: coverage improvement - JC * Opens - Testing strategy document to be sent EOD or early tomorrow, talk about this in the community meeting. - Ada - For the Community meeting on January - where to keep all the testing documentation? (not the test cases) Initially at the wiki, but define the final place (StarlingX docs?)