[Testlink-general] Testlink Fix Questions
Test & requirements management
Brought to you by:
franciscom
|
From: Jeff Hotz/T. <je...@te...> - 2005-01-17 18:24:41
|
Gentlemen,
We use TestLink for a number of our customers and plan to expand it's use.
We have a few features that we'd like implemented.
I see from your notes that you have a release due soon.
Will your upcoming release incorporate these features?
If not, I'll need to have my dev team implement them.
If we do implement them, can we get them into your upcoming release?
I have a development team and am willing to continue contributing if you
find that beneficial.
Thanks, I look forward to hearing from you
Jeff Hotz, CEO/Founder
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- TESTCo --
Few companies can test software as fast as they write it.
Our teams step in so you can go as fast as you want!
Testing. Right. Now.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
512-970-7283 | je...@te... | www.testcomp.com
>
>
> Here are the features/improvements that were requested by our
> customers or partners as of today:
>
> 1. Test cases representation is inconvenient in execution mode:
> -----------------------------------------------------------------
> In Execution mode test case formatting is corrupted because tag
> <br> is added after each row of html code which is generated
> after test case creation.
>
> 2. Impossible to create new build with letter characters:
> ---------------------------------------------------------
> It is impossible to create new build using letters, underscore
> and point, for example EPS231_RC1 or 2.40 or 2.40 A1
>
> Names that contain other characters except numbers are truncated.
>
> For example 1.1 would be truncated to 1 and, if the build 1
> already exists, error Duplicate entry '1-118' for key 1 appears.
>
> 3. Fields to track the time taken to execute a Test Case:
> ---------------------------------------------------------
> Need fields to track the time taken to execute a Test Case:
> 1. Planned Hours: to track expected/average/estimate time for each
> TC execution.
> 2. Actual Hours: the actual time taken to execute TC on a certain
> Test Plan.
>
>
|