Testers please

fridrikm at gmail.com fridrikm at gmail.com
Tue Feb 13 05:25:46 EST 2007


On Feb 13, 1:38 am, martien friedeman <martien.friede... at gmail.com>
wrote:
> I have written this tool that allows you to look at runtime data and  
> code at the same time.
> And now I need people to test it.
>
> The easiest way to see what I mean is to look at some videos:http://codeinvestigator.googlepages.com/codeinvestigator_videos
>
> It requires Apache and Sqlite.
>
> It works for me with a Firefox browser on Linux.

I'm absolutely stunned.  This is a great idea, especially because we
all hate learning other people's code, and this makes the process so
much easier.

Got some exams coming up this week, but I'll do some testing in the
weekend.

I'd like to suggest one thing though.  When evaluating conditional
statements, it would be very useful to see what "else" meant in terms
of the statement itself, for example:

if foo == 1:
    # Instead of showing "true" this would show "foo == 1"
elif foo == 2:
    # This would show "foo == 2"
else:
    # Instead of showing "false". Here comes the tricky part.  This
should show the opposite of "foo == 1", as well as the following elif
statements.  So in this case, the tab could show "not (foo == 1) |
(foo == 2)".

The reason for why showing the negated else in the header (looking for
a better word, this refers to the header shown when you click
something) would be helpful is because it helps keep track of what
statements are being evaluated, since "False" gives no information on
what statment is being tested and if the code is long, you have to
scroll way up to take a look at the if statement, so it will help a
lot with complex code.

While this is not hard to implement (unless I'm missing something),
the implementation has some problems, because conditional statements
can become very long, the else statement's tab could show an
exceptionally long statement whereas showing just "False" keeps it at
a fair length.

I might be missing something in this suggestion though - if so, please
set me straight.

At any rate, I think you've done a great job on this.  When I get
around to testing it this weekend I'll post the results on the
project's SourceForge forums.

Regards,
Friðrik Már




More information about the Python-list mailing list