Journal robi2106's Journal: Long time no see: (I know). Test DB app questions 2
I'm trying to figure out how to keep working at my current contracting company beyond my contract end date (next Wed). One thing I know they are working on is a test config DB; a system to store all the possible test configurations and the status of those tests. Unfortunately for them (and me) they are an all MS all the time shop. But I wonder if I could make some substantial progress towards a system (agile method with some real quick cycles) and peak their interest.
The system would need to be able to create new records for "revision B" of PCB board, revision X of the chip on the board, revision Y of the firmware for the chip, revision A of expansion board type Blah, firmware rev G for expansion board Blah, PDF quick start doc for entire kit Goop, etc.
The system would need to then be able to say "has this been tested before?" by looking at a "tests" section which would have some list of valid test IDs to run against a specific combination of components. The test lead would like to look at a page and see "board F + FW v0.1 + chip B + exp board J + exp board FW v0.0.2" has been tested on the following....... and then see a list / chart of tests performed, and tests not performed.
Has anyone heard of any such software? I've found TestLink via Freshmeat, TestTracking on SourceForge, TestCaseWeb (SourceForge, but hasn't been touched in 3 years), and VarTrack again on SourceForge wihthe last modificatio nat the Epoch (system time fail?). I'm not sure these are specific enough. But that doesn't mean they could not be modified to do so.
I would appreciate pointers on any commercial packages, but only so I could compare them. My goal is to find an existing project I can learn and be the admin for, or get a project to use as a good jump start for my own internally developed one.
(cross posted to my multiply account. use the user name and multiply.... if you need more clues.... I cannot help you.)
Re: (Score:2)
thanks for taking the time. I obviously want to avoid the first option, though building in some job security isn't a bad thing.... :-) But like you mentioned that would be a nightmare.
Part of the problem with this companies test tracking is that one of the things they make is like lego bricks for EEs. Expansions boards that plug into other expansion boards.
There are "kits" (generic term for everything that goes in a box and out the door) which are versioned. That "kit" could be for a main wireless contro