Beta Site release - how to test it and make sure its ready to go?

3 replies
I'm having a daily deal site to be release and my developer is at the finishing stage, however I would like to make sure that everything functions correctly? How do I do? Can I hire someone to test everything out? How do I do that?
#beta #make #ready #release #site
  • Profile picture of the author KirkMcD
    Originally Posted by smolodoy View Post

    however I would like to make sure that everything functions correctly? How do I do?
    Put it on a web server.

    Can I hire someone to test everything out?
    Sure, why not.

    How do I do that?
    The same way you hired the developer.
    {{ DiscussionBoard.errors[6792444].message }}
  • Profile picture of the author chrislim2888
    Depend on what you are testing...

    Like performance test; www.webpagetest.org/
    Load test: www.loadui.org
    Multi location test: www.locabrowser.com
    and, so on.

    This automation tools shall be used to black box check you solution. After that, you will need the dedicate tester to spot the logical bugs.
    {{ DiscussionBoard.errors[6812559].message }}
    • Profile picture of the author danielepr
      this is the so-called user-testing.
      You need to verify in real life your software with the problems and needs of your future customers.
      You really need potential future users to do that.
      You can get them on board by proposing your first version at a very low cost.
      They will find the offer very good and will purchase your software (no more than $19).
      Provide them with a forum and create a debugging platform. You can use Bugzilla (open source free) or ask your programmer to setup a table in your database to collect bugs [this should be composed of the following fields:

      - id (the identification of the bug)
      - category (you need to define a fixed set of categories. For example if you have a software which is structured as follows: add customers, manage customers, reporting, accounting --> these 4 should be the categories)
      ... you may also define other subcategories if needed... e.g. reporting: statistics, graphic, etc.
      - subject (the title of the issue)
      - description (detailed description)
      - date (the date when they open the bug/ticket)
      - status (close/open/pending)

      ..just as an example ]

      Then you create an interface for your customers to view the bugs (so they are aware of the work in progress and will verify if other users already opened similar tickets). You can also use the forum for the users and an admin panel only for your developer.

      You should not exceed the 2 weeks for testing, but of course everything depends on how your customers are active.

      Once you are confident enough you can release version 2.0 (close 95% of major bugs) and make a big launch.

      You can also ask business partners to help you testing your software especially if they need your software. You offer them free access to your tool and in return they will test your tool.

      You can also ask your testers to leave you their testimonials before the launch maybe giving them a bonus (e.g. free upgrade,...)

      Good luck

      ps available for a further private discussion if needed (I have been working as Software Project Manager for more than 20 years)... Please let me know
      Signature

      Smart Local Business Finder: www.best-marketing-ideas.com/yt/lbmt.php
      Advertising secrets never revealed in any better way: www.copywriting-videos.com/cwv/index7.php

      {{ DiscussionBoard.errors[6812648].message }}

Trending Topics