Project

General

Profile

Actions
Copy link

action #1922

closed

action #1304: Create proper test cases

Implement the model as designed by #1920

Added by aplanas about 10 years ago. Updated about 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
ancorgs
Category:
-
Target version:
Sprint 05
Start date:
2014-03-17
Due date:
% Done:

100%

Estimated time:
10.00 h
Actions
Copy link
 #1

Updated by aplanas about 10 years ago

  • Estimated time changed from 4.00 h to 10.00 h
  • Create the models as decided by #1920
  • Create the UI to manage the test matrix
Actions
Copy link
 #2

Updated by ancorgs about 10 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 50

After a lot of fighting with perl and DBIx::Class. We have the models and some preliminary UI. Not commited yet. I will create a new branch later to commit the WIP.

Actions
Copy link
 #3

Updated by ancorgs about 10 years ago

  • % Done changed from 50 to 60

New branch job_templates created in repository including the models and preliminary CRUD UI (needs a lot of polishing and tests).

Actions
Copy link
 #4

Updated by ancorgs about 10 years ago

We have detected some things that should be fixed in the models:

  • TestSuite needs a field 'prio'
  • The current format for the field 'variables' is not flexible enough
  • Product also needs a field 'variables'
  • The field variant should be also renamed to 'flavor' to match other parts of the code
Actions
Copy link
 #5

Updated by ancorgs about 10 years ago

  • % Done changed from 60 to 70

Polishing the new models and the new 'admin area' of openQA.

Actions
Copy link
 #6

Updated by alarrosa about 10 years ago

  • Target version changed from Sprint 04 to Sprint 05
Actions
Copy link
 #7

Updated by lnussel about 10 years ago

we need to be careful about what we accept as variable names in the web ui. Since those settings are exported to the environment things like e.g LD_PRELOAD must not be allowed. Maybe we should rename all variables to start with OPENQA_ or something similar to avoid side effects in the first place.

Actions
Copy link
 #8

Updated by ancorgs about 10 years ago

devel branch rebased into job_templates. A lot of git fun.

Actions
Copy link
 #9

Updated by aplanas about 10 years ago

Only to write this in some place after the sync call with Ancor: the PRIO feature need to be in the JobTemplate table, that is the one that relate the three models: (Test, Product, Machine).

The difficult part is the UI

Actions
Copy link
 #10

Updated by aplanas about 10 years ago

Another note. After talking with lnussel, the another iteration of this can go in this directions:

  • Create the key / value separation of variables, as was done in job_settings table

  • Drive / limit / control the options that the user have in the UI side (DESKTOP \in {KDE, GNOME, XFCE, LXDE})

Actions
Copy link
 #11

Updated by ancorgs about 10 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 70 to 100

Closing the issue. Polishing several things related to the parent task (and discussing with aplanas about them), rebasing, etc. I created other issues for the pending tasks.

Actions
Copy link

Also available in: Atom PDF