SPONSORS:






User Tag List

Thanks Thanks:  0
Likes Likes:  0
Dislikes Dislikes:  0
Results 1 to 3 of 3
  1. #1
    Junior Member
    Join Date
    Aug 2003
    Posts
    8
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Follow the sun testing.

    Hi,
    You probably asking your self, what is it mean follow the sun testing? so here is the explanation: we are a huge company within the company one of the group is the software grout that divided to two development sites. the difference between the two sites is 10 hours. the idea is that our group will test the other group applications and vice versa, its mean that at the morning we will have a build to test and the development team will have on thier morning a list of bugs that were found. my questins are:
    1. do any one of you ever work like this? if the answer is yes what are the tips?\
    2. what do you that we should to guide the development team in order to get an appropriate build for testing?
    3. we are using winrunner toll for our automation, is there any tips you think about that we should to think?
    4. what about the pre-testing process i mean the reqirments phase and etc. how we as a qa team will deliver our input in the erilaer stage of the development process?

    thnaks alot, poll.

  2. #2
    Member
    Join Date
    May 2004
    Location
    Netherlands
    Posts
    60
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Follow the sun testing.

    1. do any one of you ever work like this? if the answer is yes what are the tips?

    I've been working in a way like this, in a big company, but small development team. The time difference was also 8-10 hours.
    Tips:
    1 - Go travel, see each other on one table and discuss the process
    2 - Make agreements and put them on paper in detail about deliveries (when new people arrive at your company they can use this)
    3 - Keep to the agreements (but if they should be changed, do it, but make a formal process of change about the agreements)
    4 - Do not test everything twice. Make detailed testcases for 1 group, let the other execute a subset of those testcases before delivering it for a complete test.
    5 - Watch the areas that are not tested completely by both groups (because of not experience enough in something like drivers orso...). Be a watchdog on those areas.
    6 - Travel again to let someone from the other team work for a few weeks in your team and vica versa.
    7 - keep communication open, use a lot of communciation tools, chat programs, email, phone of course
    8 - Let of both teams be 1 contact person for the official builds and communication. Both teams can communicate to each other via all communication options, but when an official delivery arrives / leaves, only one person who knows it all talks to the other.
    9 - It is a dead corner: but keep reporting via formal reports about the software, with pass and fail results, etc

    2. what do you that we should to guide the development team in order to get an appropriate build for testing?

    - A good repeatable build process
    - version control
    - subset of Testteams testcases for a basic quality of the build
    (well, these are the normal things you would do in agreement with a dev.team)

    4. what about the pre-testing process i mean the reqirments phase and etc. how we as a qa team will deliver our input in the erilaer stage of the development process?
    - reviews of course

  3. #3
    Junior Member
    Join Date
    Aug 2003
    Posts
    8
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Follow the sun testing.

    thanks, it is very helpful

 

 

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.40 (Pro) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
Resources saved on this page: MySQL 11.54%
vBulletin Optimisation provided by vB Optimise v2.7.1 (Pro) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.3.0 (Pro) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
vBNominate (Lite) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 09:22 PM.

Copyright BetaSoft Inc.