Hi all,
these "rules" are ... special. The last time when logfiles were uploaded to our
internal (!) subversion server was on November 9th, 2009.
We'll discuss the content of this page after the next release.
Arsenij and Patrick asked me personally about their actual tasks for testing
and we talked face-to-face, because I knew this page was hopelessly outdated.
Best Regards,
Franz
From: Stefan Rossbach [mailto:srossb...@arcor.de]
Sent: Sunday, March 03, 2013 10:59 PM
To: Arsenij Solovjev
Cc: dpp-devel@lists.sourceforge.net
Subject: Re: [DPP-Devel] Results from TESTING
Please follow our rules for testing: http://www.saros-project.org/Testing
You missed some things like:
* Creating a Test Plan at the
TestLink?<http://www.saros-project.org/wiki/bin/edit/SE/TestLink?topicparent=SE.DPPTesting>
home page
* Go to "Test Plan Management" and click on the create button. Give a
suitable name to the test plan.
* Go to "Builds / Releases" and create a new build. We will probably
only need a single build.
* Go to "Add / Remove Test Cases". Choose the test cases you identified
earlier.
After the test:
1. All test participants store their log files in Subversion at
https://svn.mi.fu-berlin.de/agse/sci/dpp/testing/logs/... and send an email to
the list telling the others that they have done so
* Alternatively if log files are small: Test participants send their
logs to the list for the TM to upload to SVN.
1. All test participants search their log files for "FATAL", "ERROR" and
"WARN". All of these should be collected into an email to be sent to the
mailing-list. This should be done no later than 4pm on the test day.
2.
Am 22.02.2013 17:16, schrieb Arsenij Solovjev:
Hallo dear devs,
There is one critical bug, no regressions and a few mildly irritating things.
The critical bug:
a) Session-6 doesn't work: the host always gets his favorite color, no matter
which
color it had in a previous session with the same contact.
A few mildly irritating things:
a) The colors in the SUC change to the Session colors as soon as a session is
started,
and revert to the old grey and cyan (which don't look pleasant anyway) when the
session ends.
b) We couldn't reproduce bug #3458952 on the old release.
Both the new and the old release displayed the same kind of behaviour:
- A invited B and B accepted and chose a project location.
- While B was modifying a shared file the whole time, a session negotiation
is started with C
- B got restricted to read-only, and couldn't regain permissions (The grant
write-access context menu item, was greyed out on the host's side)
BR,
Arsenij and the test team
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
DPP-Devel mailing list
DPP-Devel@lists.sourceforge.net<mailto:DPP-Devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/dpp-devel
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
DPP-Devel mailing list
DPP-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dpp-devel
