You are here

Development Test or Pre-Release: Comments Template

5 posts / 0 new
Last post
powerjuce
powerjuce's picture
Offline
Last seen: 11 years 9 months ago
Developer
Joined: 2007-09-20 21:34
Development Test or Pre-Release: Comments Template

As a way to help testers as they are testing new apps as they came, i came up with a series of templates.

The idea is to always to use the general stuff so that dev knows what the general info is and then pick the template you want to use

here they are:

General Information

    General Stuff

  • OS:
  • Rights:
  • What Release(Dev test # or Pre-Release #):

Here is the code for it

<ul><strong>General Stuff</strong>
<li>OS: </li>
<li>Rights: </li>
<li>What Release(Dev test # or Pre-Release #): </li>
</ul>

Paf specific Information
main dir

  • Problem
  • App dir
    • Problem
    • AppInfo dir
      • Problem
    • (Appname) dir
      • Problem
    • Default Data dir
      • Problem
  • Data dir
    • Problem
  • Other dir
    • Problem
    • Help dir
      • Problem
      • images dir
        • Problem
    • Source dir
      • Problem
      • Code
        • Problem

Here is the code to make it happen

<strong>main dir</strong>
<ul>
<li>Problem</li>
<li><strong>App dir</strong>
<ul>
<li>Problem</li>
<li><strong>AppInfo dir</strong>
<ul>
<li>Problem</li>
</ul>
</li>
<li><strong>(Appname) dir</strong>
<ul>
<li>Problem</li>
</ul>
</li>
<li><strong>Default Data dir</strong>
<ul>
<li>Problem</li>
</ul>
</li>
</ul>
</li>
<li><strong>Data dir</strong>
<ul>
<li>Problem</li>
</ul>
</li>
<li><strong>Other dir</strong>
<ul>
<li>Problem</li>
<li><strong>Help dir</strong>
<ul>
<li>Problem</li>
<li><strong>images dir</strong>
<ul>
<li>Problem</li>
</ul>
</li>
</ul>
<li><strong>Source dir</strong>
<ul>
<li>Problem</li>
<li><strong>Code</strong>
<ul>
<li>Problem</li>
</ul>
</li>
</ul>
</li>
</li>
</ul>
</li>
</ul>

Registry entry Information

    Registry Entries Left Behind

  • Entry 1
  • Entry 2

Once again here is the code

<ul>Registry Entries Left Behind
<li>Entry 1</li>
<li>Entry 2</li>
</ul>

Error logs are exactly like the title

Error Logs
Here is the code:

<strong>Error Logs</strong>

General Errors

    General Errors

  1. Error 1
  2. Error 2

Here is the code to do this

<ol>General Errors
<li>Error 1</li>
<li>Error 2</li>
</ol>

Comment with suggestions or ideas
I hope this will made it easier for people to test and comment on apps

LOGAN-Portable
LOGAN-Portable's picture
Offline
Last seen: 9 years 10 months ago
Developer
Joined: 2007-09-11 12:24
I have mixed feelings. Yes

I have mixed feelings. Yes people should mention what version was tested and on what OS and version, but the extended markup might cause people just to ignore it because it might take much time to make it look good.

To me this might be enough:

ApplicationName Portable v1.234 on Win 2000 Pro (SP4)
- A problem with this
- A problem with that
- And maybe a remark

My guess it if you keep it simple it's complex enough Smile

Simeon
Simeon's picture
Offline
Last seen: 8 years 1 month ago
DeveloperTranslator
Joined: 2006-09-25 15:15
ditto

As much as I welcome your effort and as much as I dislike the un-useful test comments, I am with LOGAN that it might scare users away if the error report is a corset like this.

"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate

LittleUnkn0wn
Offline
Last seen: 10 months 4 weeks ago
Joined: 2006-11-02 11:09
I also agree with LOGAN, but

it would just be a suggested format, so more technical people could use it, but it wouldn't hinder your every-day user/tester.

powerjuce
powerjuce's picture
Offline
Last seen: 11 years 9 months ago
Developer
Joined: 2007-09-20 21:34
yea that was sort of what i wanted this to be...

This was really just a suggestion to make it easier to comment

The only thing I felt should be put up was the general Infomation.

I mean that way both the Devs and other testers kno what version the error popped up in.

Please search before posting. ~Thanks

Log in or register to post comments