action #301
closedWrite needle DB query API
100%
Updated by aplanas about 11 years ago
- Assignee set to coolo
- Due date set to 2013-04-19
- Estimated time set to 10.00 h
- Start date changed from 2013-04-03 to 2013-04-17
Updated by coolo about 11 years ago
- Status changed from New to Feedback
Alberto - can you specify a bit better what you expect from this?
Right now we have needle::tag("inst-bootmenu") which returns an array of needles. What else do you have in mind?
Updated by coolo about 11 years ago
- % Done changed from 0 to 20
I'm doing some DVD installations to get some needles in the database to actually play with queries
Updated by aplanas about 11 years ago
Yeah sorry. There is a task (#310) that need to remove or add a set of needles before a set of test will run. The example was the 'Text mode installation', to avoid match with a graphic needle, we need to recover only the needles that are for the Install stage && Text mode.
You created new tags for that, so the recover of these needles are possible, but we need to expand a bit the needle API: .remove() .add()
Updated by aplanas about 11 years ago
- Status changed from Feedback to In Progress
Updated by aplanas about 11 years ago
- Due date changed from 2013-04-19 to 2013-04-05
- Start date changed from 2013-04-17 to 2013-04-04
Updated by coolo about 11 years ago
Use cases:
- remove needles that match "installation", but not "TEXT"
- query needles that match "desktop" and "KDE"
- remove needles that match "TEXT"
Updated by coolo about 11 years ago
waitforneedle("desktop KDE") will now match only needles that have them all.
Updated by coolo about 11 years ago
- Status changed from In Progress to Resolved
use case
for my $n (@{needle::tags("installatin)}) {
$n->unregister() unless $n->has_tag("TEXT");
}use case
needle::tags("desktop KDE")use case
for my $n (@{needle::tags("TEXT")}) {
$n->unregister();
}
Updated by aplanas about 11 years ago
- % Done changed from 20 to 100
- Status changed from Resolved to Closed