home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Talk
Stability Release
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="wietze" data-source="post: 20104" data-attributes="member: 13604"><p>Hi, </p><p></p><p>I will send you the file tonight because i am on my work now.</p><p></p><p>I agree with you that a report must have the basic information and a sort of standard layout. But we want to test diffrent things in each test, so we must make a new report for each test with specific info and tests. There must be someone who's making these reports.</p><p></p><p>The first thing is that the report it self is simple and easy to use, never the less it gifs a lot of information </p><p></p><p>Naturaly we want to rule out that testers give false information because their system is corrupted, i think that potential testers first have to benchmark their system so we can analize that the problems do not come out of the system. This make it better to find out if problems are related to low or high performance systems, and or specific hardware. The results of these benchmarks must be mailed to the "Manager"of the test team or someone who capture the data.</p><p></p><p></p><p>I am pleased that there are things going to improve the program, but i find it strange that there are not manny comments from the dev team in this thread. I hope that the Dev's are pleased with this, and i would like that they give a statement on their position.</p></blockquote><p></p>
[QUOTE="wietze, post: 20104, member: 13604"] Hi, I will send you the file tonight because i am on my work now. I agree with you that a report must have the basic information and a sort of standard layout. But we want to test diffrent things in each test, so we must make a new report for each test with specific info and tests. There must be someone who's making these reports. The first thing is that the report it self is simple and easy to use, never the less it gifs a lot of information Naturaly we want to rule out that testers give false information because their system is corrupted, i think that potential testers first have to benchmark their system so we can analize that the problems do not come out of the system. This make it better to find out if problems are related to low or high performance systems, and or specific hardware. The results of these benchmarks must be mailed to the "Manager"of the test team or someone who capture the data. I am pleased that there are things going to improve the program, but i find it strange that there are not manny comments from the dev team in this thread. I hope that the Dev's are pleased with this, and i would like that they give a statement on their position. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
Stability Release
Contact us
RSS
Top
Bottom