SPONSORS:






User Tag List

Thanks Thanks:  0
Likes Likes:  0
Dislikes Dislikes:  0
Results 1 to 5 of 5
  1. #1
    Member
    Join Date
    Oct 2005
    Location
    QA Test Engineer
    Posts
    54
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    How to test small projects effectively?

    Hi
    In our company,we have lot of small projects.But we don't have any proper requirement or solution docs.We have only templets & the mail conversation between the client & our PM. We have only minimum time to test.
    What can i do to test the project effectively?

    Regards,
    Mark Rajesh

  2. #2
    Senior Member
    Join Date
    Mar 2003
    Location
    Uk
    Posts
    214
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: How to test small projects effectively?

    Have these projects been been completed or are they still on the build?
    If they are still on the build, then you could do something called "daily build and smoke test".Run some Smoke tests, to cover the major functionality for Breadth rather than Depth.

    Run through some tests and give it a new name called Sham tests.
    Cheers,
    Suresh


    http://cognitive-content.blogspot.com

    It is not necessary to change. Survival is not mandatory -W Edwards Deming

  3. #3
    Senior Member
    Join Date
    Sep 2003
    Posts
    114
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: How to test small projects effectively?

    The size of the project should probably affect the way you manage your requirements, design etc.

    However, the fact that the project is small should *not* lead to the conclusion there is no need for any formal specification....

    So, your question should not be how to test effectively, but how to manage such a project effectively....

    Lidor
    Lidor Wyssocky
    http://www.QualityAspect.com

    Visit The Mindset - Lidor Wyssocky's blog on Optimizing Software Development
    http://blog.QualityAspect.com

  4. #4
    Member
    Join Date
    Oct 2005
    Location
    QA Test Engineer
    Posts
    54
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: How to test small projects effectively?

    Hai,
    Thank u so much for ur responses.
    Now i am very clear about how to manage small projects.I had a discussion with my PM & ask him to give all the details they have provided to the developer.Now I am also in group,whenever our team have call with the client.This is very useful & meaningful.Thank u so much

    Regards,
    Mark Rajesh
    Chennai,India

  5. #5
    Senior Member
    Join Date
    Jun 2000
    Location
    Charlotte, NC, USA
    Posts
    617
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: How to test small projects effectively?

    Is there sufficient information in the mail conversation (oh my!) to unambiguously test for the expected functionality?
    You may want to talk with the PM to understand how they are interpreting the information from client and passing it on to the development team.
    You may want to talk to the development team to find out what they are developing against.

    Somehow, somewhere, there's a trail of communications that is sufficient for the work to get done and done correctly.

    If not, then it's likely the client is VERY UNHAPPY! in which case, you shouldn't have any trouble convincing the PM that a) more thorough project documentation is needed, b) you need to be in the loop when they are talking to either the client or the developers, c) you need more time to test.

    It's possible to streamline the documentation significantly, combining a Business and Functional Requirement for example.

    We have a process that applies to any changes projected to take < 80 hours total project effort. There is a single document that describes the problem and the proposed solution. There is sufficient information in the document to allow developers to do their work and for QA to do their testing. The test documentation is correspondingly streamlined. A simplified test plan, the necessary test cases, etc.
    You end up executing an abbreviated regression and checking the specific changes indicated by the documents.

    This works as long as the application is well understood and the process is followed.
    Resistance is futile.

    SuperK

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Search Engine Optimisation provided by DragonByte SEO v2.0.36 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Resources saved on this page: MySQL 10.00%
vBulletin Optimisation provided by vB Optimise v2.6.4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.2.8 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominate (Lite) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 04:06 AM.

Copyright BetaSoft Inc.