Home Forums General Welcome

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

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

    Welcome to the bulletin board! Please post your comments, suggestions, queries, announcements, anything at all related to open-source testing!


    Profile photo of pkaluski

    Hi All,
    I am an IT Consultant with 7 years of experience in software development. I am currently seriously exploring the subject of using open source tools for testing.
    I have few suggestion about this forum:

    To Admin:
    Please let people be more specific about their job. Let them write how experienced they are, were do they work, what do they do currently.

    To members:
    Once given this new feature mentioned above – use it

    I consider this important and let me tell you why.

    People experienced in the business, know that the single most important thing before you start using a new tool is to:


    Commercial software vendors developed the impressive machinery for convincing managers that using their tool is the single most intelligent decision ever made.
    There is no such thing in open source.
    Successfull experience of others may be a mean to convince your supervisors. Positive opinions about some tool as well. But this opinions must be given by professionals, which are proud of their experience and are not affraid of being contacted. Bunch of posts made by UPO (Unidentified posting object :lol: ) are not a good material for starting a conversation with your manager.
    Success stories are invaluable. Share them with us. It would be a great help for whole open source testing community.
    If you have a big, well known name or are somehow linked to well known product dont be shy. Let all people know that open source testing is of interest of respected professionals.


    Profile photo of majek

    Hi Piotr,

    I agree, this would be great if opensource products would have so good marketing and PR as commercial products but I they dont and it is hardly possible that they will have such. There are several reasons:

    1) most OS projects leaders are hackers who do it in their free time and are more interesting in coding than in advertising. They use freshmeant, sourforge, savannah and thats all. They cant, have no time or just dont feel like to do the PR job.
    2) most OS products are not complex solutions. They cover rather small aspect of development process, there have hardly anything in common. They are not unified. If you want to build good testing platform based on opensource projects you must assemble it from many different subprojects written in many different languages. Thats not a good point in the discussion with the boss… What could we say? “Hey boss. Ive great testing platform. We only must hire one Java specialist, one for Python, one for Perl, we must lern only 120 new tools and make it work togother. Well receive help from talented community: well just subscribe to 120 mailig lists…”. Sorry for the sarkasm but this is todays reality.

    Im not against OS. I lead one OS, test-related project myself and think that OS and development based on community is the future of software development but on the other hand OS movement is not ready to provide a total, easy to use, unified replacement of commercial software. I hope that in the near future it will change.

    Profile photo of pkaluski

    Hi Majek,
    Your post touches major concerns related to using open source testing and to some extent I agree with you. But there are some areas when I tend to disagree.
    As for the first point of your post. Of course, I did not think about OS developers doing advertisement. What I had in mind are people who USE open source (not develop) in their job. Perl, Linux are being used by big companies for doing serious, business critical processing. So what I ment was, that people who use OS testing tools in real business tell us about it.
    As for the second point of your post I thing that your point is valid but you exagerated too much. And I dont agree with your vision of what is needed in a long term. These two issues seem to be tightly related so address them together.
    One important point. As I have written in my first post, I am beginning exploring OS testing tools, so my experience is small. My response below is based on my experiece as a developer, which I think may be somehow mapped on OS testing.
    So… Yes, lack of unification is seen by managers as a major problem. But is it actually a problem? Do unified tools offer easyness and cost effectiveness they promise? My experience say they dont. They offer many features, which in many cases you are never going to use. And their prices are OUTRAGES. You have written that using OS requires additional hires. But this is also the case for Commercial Testing tools. Sure, everyone can run a recorder for recording simple GUI script. But creation of a suite of GUI scripts, constituting a framework of reliable tests is totaly different story and requires much more effort then it is written in documentation or said on commercial presentations.
    Indeed, when you want to use open source tools you need two hire 2 people (not 120 :) ). One has to know say Java and perl, the second Python and Tcl (for example). Learning these languages requires time, but there are excelent learning resources and communites for each of them, and they are for free. This is not the case for a leading commercial software. Trainings are expensive and documentation is not free. And learning this software also takes time. So when buying commercial testing software you will also have to hire new people.
    And finaly, is unification such a good thing? Are those monolythic “Lets do everything in the only right way” tools better then the mixture of small tools doing small things, maybe in different manner, but doing them right. I think it is quite the oposite. Small, well defined tools gives you oportunity to pick what you really need and to configure them in many ways. Sure, you need a knowledge to do it. But there is no path in IT, which does not require knowledge. If someone is telling you something different HE/SHE IS LYING. It may seem on the beginning, that you can do complex things easily, but sooner or later this lack of knowledge is going to bite you in the leg in the least expected moment.
    There is an interesting thread in QAForums about commercial vs OS testing tools for GUI automation … 001973;p=1. Opinions are divided.

    Anyway I repeat, please share your experience with us.

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

You must be logged in to reply to this topic.

New User?

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