Categories

    Tags

Feature-comparison on Opensourcetesting.org

Home Forums General Feature-comparison on Opensourcetesting.org

This topic contains 3 replies, has 1 voice, and was last updated by Profile photo of Admin Admin 11 years, 1 month ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #1922
    Profile photo of Admin
    Admin
    Keymaster

    Hello to all,
    first of all, I was very glad as I found this site. I find its great.
    Now a suggestion, how about comparison of the similar tools.
    This could be a simple table with one column per a tool. Each row
    describes a feature. Every cell contains “present/not present” or
    a note how good the feature is implemented.

    I know it is not easy. And it is even harder to make the appraisal
    objective. But though it would be better than nothing for one who
    has to decide between 20 tools.

    I could contribute to:
    -Mantis
    -CppUnit
    -Could evaluate any C++ based or related tools

    Looking forward for replies.

    #1923
    Profile photo of markab
    markab
    Participant

    Thats an excellent idea, thanks Valentin, I think it would really help users of the site select and evaluate tools. Ill have a think over the coming week about how this can be implemented. As all the tool details are stored in a database, such a table could easily be generated, but as you say, the actual investigation task would be time consuming, and I have very little time (I have a day job by day, and a small baby by night!)

    The easiest way may be for volunteers to each take a tool type (e.g. functional, bug databases, java unit testing) depending on their area of expertise, and supply a list of common functionality (which will differ for each tool type). I already have a comparison list for bug databases somewhere at work I think, Im sure many other test managers and analysts amongst you will have your own comarison lists compiled for different tool types as part of prior evaluation processes too. Feel free to forward me any if so. ([email protected])

    Once I have the list of common functionality for each tool type, I can then post a list of tools that users can submit individually. Im sure this could be handled dynamically using web forms, so neednt be too timeconsuming from an admin point of view. I have direct contact with about a quarter of the tool developers who submitted their own tools, I expect these guys would be happy to submt their own, which would be a good start.

    Will post more info in due course,
    Thanks
    Mark

    #1924
    Profile photo of Admin
    Admin
    Keymaster

    Hello Mark,

    I found this article very interesting:
    http://www.gamesfromwithin.com/articles … 00061.html
    It compares several unit-testing frameworks.
    After reading this article I am not quite sure, that a feature table would be
    really a big h***. I find the approach of the author of
    “Exploring the C++ Unit Testing Framework Jungle” very good.
    -He sets his own criteria first, tells his requirenments to the framework
    -He describes the minimal efford needed, to get the framework running
    -He tells what is his favourite (imo very essential!)

    After working through the article this morning we decided for CxxUnit, evaluated it and integrated in our project within 3 hours!
    In contrast – tt tooks me some weeks, till i evaluated dozens of bug-databases and finally decided to take mantis.

    So, I just whanted to say, such an article for each category of tools would be also a big help.

    Have a nice week end!

    #1925
    Profile photo of Dimon
    Dimon
    Participant

    [quote="Anonymous":3q75rngy]Hello Mark,

    I found this article very interesting:
    http://www.gamesfromwithin.com/articles … 00061.html
    It compares several unit-testing frameworks.
    After reading this article I am not quite sure, that a feature table would be
    really a big h***. I find the approach of the author of
    “Exploring the C++ Unit Testing Framework Jungle” very good.
    -He sets his own criteria first, tells his requirenments to the framework
    -He describes the minimal efford needed, to get the framework running
    -He tells what is his favourite (imo very essential!)

    After working through the article this morning we decided for CxxUnit, evaluated it and integrated in our project within 3 hours!
    In contrast – tt tooks me some weeks, till i evaluated dozens of bug-databases and finally decided to take mantis.

    So, I just whanted to say, such an article for each category of tools would be also a big help.

    Have a nice week end![/quote:3q75rngy]

    Lets first make such form-description for each tools (every tool have to be on individual page):
    – Name (present)
    – HomeSite (present)
    – Requirements (present)
    – Sourceforge activity (present)
    – Platform/OS (not requirements, because it for client part if possible)
    – Screen Shots (smaaaall :-) )
    – Parameters(many) (self for each tools, for future)
    – Advantages – “pluses”
    – Weakness – “minuses”
    – Comments or Quotes
    maybe something others fields.

    And have a short description
    – Name / Homesite
    – Platform/OS
    – Average Quote / Comments Number

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

You must be logged in to reply to this topic.

New User?

Register
Do NOT follow this link or you will be banned from the site!