incubator-bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olemis Lang <ole...@gmail.com>
Subject Re: [BEP-0003] #355 - Summary of the work done towards multi-product support (2013-02-16)
Date Thu, 21 Feb 2013 21:07:31 GMT
On 2/18/13, Olemis Lang <olemis@gmail.com> wrote:
>
[...]
>
> TODO-1: Immediate conclusion => there is a lot to fix yet .
>
> For a more detailed report and trendings please see this spreadsheet [1]_ .
>
> What is in the test suite ?
>
> Only unit tests making use of product environments . That leaves
> functional TCs (see #387) , doctests (see #385) and a few other test
> cases (see #396) out of the equation . We'll deal with those
> afterwards . In terms of subsystems the situation is as follows :
>
>   - Ticket TCs are almost done
>     * TODO-2: There's an urgent need to implement something important we
> are
>       missing, and it is product-specific ticket sequence.
>       At the moment ticket ID in product scope is taken as the global
>       (i.e. unique) ticket ID , which is not accurate . Most test cases
>       pass but the underlying implementation is ignoring this particular
>       enhancement.
>     * TODO-3: The only missing piece of the puzzle are wiki syntax TCs
> (see #390)
>       which MUST make explicit use of the output of TODO-2
>     * TODO-1.1: make query TCs pass
>     * Functional TCs postponed until a later iteration
>   - All relevant TCs for the wiki subsystem have been translated
>     * TODO-1.2: Some test cases for wiki formatter , macros and
>       syntax are failing .
>     * Functional TCs postponed until a later iteration
>   - All relevant TCs for admin console have been translated
>     * TODO 1.3: fix failures
>     * Functional TCs postponed until a later iteration
>   - All relevant TCs for MIME API have been translated . They seem to be
> ok.
>   - There are no unit tests among preferences TCs , so they won't be
>     considered in this iteration (unless otherwise stated) .
>   - There are no tests for built-in search but this is not a concern as
>     our free-text search plugin does a good job on this direction.
>   - A relevant subset of TCs for core features has been translated (i.e.
>     attachments, configuration, environments, notification, permissions)
>     * TODO-4: Document and implement product-specific resources
>       hierarchy
>     * TODO-5: Translate Trac resources and wiki syntax TCs
>   - There are no unit tests among timeline TCs , so they won't be
>     considered in this iteration (unless otherwise stated) .
>   - TCs for util package are at a lower level of abstraction so
>     they won't be considered in this iteration (unless otherwise stated) .
>   - TODO-6: Translate all TCs for Trac version control subsystem
>   - TODO-7: Translate all TCs for Trac web API
>

FYI

Done : TODO-1.3, TODO-7 (sessions)
Later today : TODO-1.1, TODO-1.2, TODO-5
Work in progress : TODO-3, TODO-7 (chrome)
Not started : TODO-2, TODO-4, TODO-6

>
>
> .. [1] Trend of Trac test case conversion towards Bloodhound
> multi-product support
> (https://docs.google.com/spreadsheet/ccc?key=0AqniOh7YBqF4dHp6Sk0zWkNxS2FpMjZHQWllbmhYMnc#gid=0)
>

-- 
Regards,

Olemis.

Mime
View raw message