Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

User Story #5 (new)

Opened 18 years ago

Last modified 17 years ago

Generate Testdata for Search

Reported by: sfrank Owned by: jamoore
Priority: major Milestone: Unscheduled
Component: Search Keywords: n.a.
Cc: Story Points: n.a.
Sprint: n.a. Importance: n.a.
Total Remaining Time: n.a. Estimated Remaining Time: n.a.

Description (last modified by sfrank)

In order to properly test the Search (and maybe other parts of the system too), we have to be able to generate a defined set of testdata and populate the database with it.

This testdata-setup has to fulfill the following requirements:

  • known quantities (how many images, annotations)
  • known attributes (keywords in annotations etc.)
  • reproducible (has to be included in setup and teardown for tests)

Only if these requirements are fulfilled, testing the search makes sense, as you now have proper and predictable values for asserting the search-results.

NOTE: Importing testdata from an existing system is unfortunately not sufficient for testing the search. This testdata has to be indexed to be found, therefore the indexing has to run after the import - as I do not (yet) know how to do that, I have postponed this task to #99.

Change History (12)

comment:1 Changed 18 years ago by sfrank

  • Summary changed from Have a Database populated Database with Images to Have a Database populated with Images

comment:2 Changed 18 years ago by sfrank

  • Component changed from build to search
  • Owner changed from jmoore to sfrank

comment:3 Changed 18 years ago by anonymous

  • Keywords iteration1 added

comment:4 Changed 18 years ago by sfrank

  • Description modified (diff)

The easiest way to fulfill this requirement would be to use whats coming out of #48 (Importing testdata). We also discussed setting up Resurect for this, but this looks like seriously more work. We'll use, whatever is finished first.

comment:5 Changed 18 years ago by sfrank

Implementation will work like this:

  • setup a postgres-database
  • import a dump provided by an existing omero-installation

comment:6 Changed 18 years ago by sfrank

  • Keywords iteration2 added; iteration1 removed

comment:7 Changed 18 years ago by sfrank

  • Description modified (diff)
  • Summary changed from Have a Database populated with Images to Generate Testdata for Search

comment:8 Changed 18 years ago by anonymous

  • Keywords iteration4 added; iteration2 removed

comment:9 Changed 18 years ago by sfrank

  • Keywords iteration4 removed
  • Milestone changed from 3.0-M2 to 3.0-M3
  • Version changed from 3.0-M1 to 3.0-M3

comment:10 Changed 18 years ago by sfrank

  • Keywords iteration4 added
  • Status changed from new to assigned

comment:11 Changed 18 years ago by cxallan

  • Keywords iteration4 removed
  • Milestone changed from 3.0-M3 to 3.0-M4
  • Version changed from 3.0-M3 to 3.0-M4

Plopping these in M4.

comment:12 Changed 17 years ago by jmoore

  • Milestone changed from 3.0-Beta2 to Unscheduled
  • Owner changed from sfrank to jmoore
  • Status changed from assigned to new

Unscheduling all search tickets. See #706 and wiki:proposals/Search

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.68750 sec.)

We're Hiring!