• Author
    Posts
  • #4248
    @raymond-oconnor-167

    Hi, looking for some of you experiences with test case management. What repositories do you use? How do you get your team to write test cases in a standardized way, so that the effort required can be measured and repeated. Also I’m interested in keyword driven testing? Does this methodology only apply to automation or could you build a battery of manual tests with this approach?

    Thanks

    Ray

    #4378
    @padmaraj

    Hi Raymond O’Connor,

    I like to divide your question in more parts to answer myself in “logical way” and other experts may answer in more advance way from this community.

    This question faced by many test consultants 🙂

    1. What repositories do you use test case management?
    Ask question to yourself or your client
    (Requirement engineering comes in to play here)
    • Cost/budget of client
    • Tool must ease of use
    • Tester not required extensive training to your selected tool ( easy to use )
    • Easily configurable in different environment
    • Able to Integrate with Jira / redmine ..etc for defect tracking software
    • Tool need Integrates CI software’s for running automation

    2. How do you get your team to write test cases in a standardized way, so that the effort required can be measured and repeated?

    • First teamneed to understand the requirements, tell them to draw a block diagram about product/domain on the paper so give some days or hours’ time according to your time and budget to understand them ( domain / product ) .
    • Make small meeting in between to tester to explain what they understand about the product / domain.
    • Now tell them to divide the product on base of functionality. ( example when disassemble the pc you see many components ) & tell them to identify the core product functionality, its help a lot on different kind of testing’s for testers.
    • Clear guide them to use how to write a test case heading., its help to sort them easy teats cases from the system(jira/redmine)
    • Routine changes in between testers with product functionality, normally 1 tester not able to test all functionality. ( we never think same on any object, and not able to identify and solve all problems )
    • Build the communication between testers and developer and products owners – try to bring them on one platform ( devops ) to get high quality software.

    3. Keyword driven testing?
    • In simple words divide big things in to small part and name them to make your life easy, its help to easy to trace and save a lot of time.

    4. Does this methodology only apply to automation or could you build a battery of manual tests with this approach?
    • 100% test automation joke of the ” test engineer”.
    • Software you are testing most of time used humans only.
    • When you run automation test and manual test, high chance you get different bugs. Mean you need an extra person to track and understand those all.
    • Sepnd more time to do some research what you testing, from which process you get more befit. Either from “Automation Testing or Manual Testing”

    Padmaraj

    #17005
    @ronan

    This post might be a useful read for you.

    #17062
    @abhilashawaghm11

    <p lang=”en-US” style=”box-sizing: border-box; margin: 0px 0px 24px; color: #141412; font-family: ‘Source Sans Pro’, Helvetica, sans-serif; font-size: 16px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: #ffffff; text-decoration-style: initial; text-decoration-color: initial;”>A best practice is a way to deal with something that gives a good outcome when implemented wisely. In case of testing, best practices incorporate numerous things, e.g. risk-based testing, goals of testing, validation and verification and so forth.</p>
    <p lang=”en-US” style=”box-sizing: border-box; margin: 0px 0px 24px; color: #141412; font-family: ‘Source Sans Pro’, Helvetica, sans-serif; font-size: 16px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: #ffffff; text-decoration-style: initial; text-decoration-color: initial;”>We should have a concise dialog on four of the best practices of manual testing to help oversee time and endeavors of a tester with a specific end goal to have a sans bug application.</p>
    <strong style=”box-sizing: border-box; font-weight: bold; color: #141412; font-family: ‘Source Sans Pro’, Helvetica, sans-serif; font-size: 16px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: #ffffff; text-decoration-style: initial; text-decoration-color: initial;”>1. Test plan preparation:
    <p lang=”en-US” style=”box-sizing: border-box; margin: 0px 0px 24px; color: #141412; font-family: ‘Source Sans Pro’, Helvetica, sans-serif; font-size: 16px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: #ffffff; text-decoration-style: initial; text-decoration-color: initial;”><strong style=”box-sizing: border-box; font-weight: bold;”>2. Documentation and maintenance of test cases:</p>
    <p lang=”en-US” style=”box-sizing: border-box; margin: 0px 0px 24px; color: #141412; font-family: ‘Source Sans Pro’, Helvetica, sans-serif; font-size: 16px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: #ffffff; text-decoration-style: initial; text-decoration-color: initial;”>The key factor involved in testing is the creation of test cases. Test cases ought to contain exit and entry criteria, which make the work process considerably simpler.</p>
    <p lang=”en-US” style=”box-sizing: border-box; margin: 0px 0px 24px; color: #141412; font-family: ‘Source Sans Pro’, Helvetica, sans-serif; font-size: 16px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: #ffffff; text-decoration-style: initial; text-decoration-color: initial;”>also check detail http://crbtech.in/Testing/best-practices-follow-case-manual-testing/</p&gt;

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.