[Red5] test-plan / check-list / standard-cases for releasing/testing Red5?
seba.wagner at gmail.com
Sun Oct 5 11:42:52 PDT 2008
yes okay but also if you support multiple client side technologies,
somewhere you need to start testing.
Saying *the field/technologies we use/allow is too wide lets wait 'till
somebody comes and complains about xyz* will not solve problems and bring
red5 to a more stable state.
So if you start a standard scenario in any (AS3 or AS2 or OpenLaszlo) and
build a sample based on Java5 or Java6 that should be sufficient to get
started. Later on you can port that to your needs but you got at least a
standard case which IS working.
Other testing areas would be then OS specific/related areas, this is not
connected to any technology question. If the standard case does run on all
qualified Plattforms (I guess you test osx, win, Linux) then it will run no
matter if its AS2 or AS3 or any other technology.
Later on you maybe have the chance to do that automatically by ant/JUnit
like for example in the OpenLaszlo build process. Cause no one will do
endless checks like on that list by hand:
after each update.
But there is a need for something to verify that features are working and to
get structure in the test-release thing.
2008/10/5 Sascha Sauren <sascha.sauren at googlemail.com>
> it think thats an good idea, but i there would be also a general problem.
> to many diifferences between clientside eg. openlaszlo, AS2, AS3 flash and
> AS3 flex clientsieded could implement the same functionality but for some
> reasons they got interpreted different, besids the servsided capabilty tu
> use scripting instead java there are 2 java versions (5,6) and os dependend
> problems. so a testapplication would be very complex.
> one idea would be if some from the list would be testers for their usecase
> and their os, and if someone has a problem other testers could try to
> reproduce the same error on their side,
> may this also helps the core team, to sort out trunk related questions from
> functionality questions or questions regarding the stable version, and help
> those whant to use the trunk and accept that there may could be some
> problems with it, but thats just a thought.
> to get back to testcases and better logging...
> i think for ur testcases u run red5 in eclipse, and watch the logfiles...
> please try instead....
> * window/perspective > debug
> * get back to java perspective by just clicking the "java" perspective
> button to the top right corner
> * from the menu click: run > DEBUG AS > Junit Test
> for further informations about this u might whant to read about Junit tests
> (which are made to test all use cases)
> try google, sorry iam also new to that:D and dont want to tell u something
> greetz Sascha
> 2008/10/5 Sebastian Wagner <seba.wagner at gmail.com>
>> I was wondering if we could develop a simple test-app for red5 to run all
>> critical functionality.
>> What do you think? Should be no problem to build that on top of one of the
>> Demo's. Nothing shiny just for testing.
>> Based on that there could be a check-list which is tested before every
>> or are you already using something like that internally? I can not see
>> something like that in the wiki or somewhere.
>> The thing is that I always run in a lot of different Issue's using red5.
>> And instead of searching for:
>> *Is it my custom-app fault* or *Is it a Bug inside Red5*
>> Some standard cases to check functionality could make it more easy to
>> ensure the quality and
>> also makes it more easy to refer to them if something is broken.
>> what do you think?
>> Sebastian Wagner
>> seba.wagner at gmail.com
>> Red5 mailing list
>> Red5 at osflash.org
> Red5 mailing list
> Red5 at osflash.org
seba.wagner at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Red5