testing - Is there an Acceptance Test management approach that can live with the code in git? -
testing - Is there an Acceptance Test management approach that can live with the code in git? -
we moving acceptance test driven development approach defining features. seems working well, we're starting run issues test management. @ moment, utilize sharepoint/excel track acceptance tests. because non-technical customers, qa , dev update tests. problem tests don't live code, aren't branched/versioned along code, , manual. we're looking @ total on test case management software (e.g., zephyr, testrail, etc), feels little heavy, , test info still doesn't live code.
is there test management application friendly non-devs, stores info in way work git? trying maintain tests alongside code fool's errand?
thanks, erick
yes, thought maintain tests code.
one framework utilize accomplish goal fitnesse. known test management tool supports collaboration between business guys, developers, , testers. git plugin fitnesse can maintain tests within git repository.
we maintain our acceptance tests, based on framework named concordion, in our source code repository. concordion specifications consists of 2 parts: well-formed html document describing functionality, , fixture code written programming language of application such java or c# finds concrete examples in document , uses them validate scheme under test.
our executable specifications written wysiwyg html editor such microsoft webexpression or bluegriffon product owner or testers. maintain them in our repository , access them via tortoisegit, works members of our team have technical background. involve non-technical need write little script pulls latest updates local repository, start editor of choice, , force changes after editing central repository.
please, note there concordion extension excel available, enables specify test info (i.e. input , expected output values) in excel spread sheet , utilize test application.
imho testing sort of detailed analysis in software projects. many details not discussed , specified, testers job of thinking details of feature. unfortunately, happens after developers did work, causes lot of rework , additional cost. thus, base of operations on atdd effort should seek improve collaboration of team on specifications before head test automation.
please, have @ talk of gojko benefits invest 5-10% of sprint define details collaboratively. specification work in our team has improved lot since specification workshops based on ideas of specification-by-example.
git testing bdd acceptance-testing atdd
Comments
Post a Comment