FOSSology

{{toc}}

h1. Cluster Test Cases

Below is a list of cluster test cases to be executed by one or more members of the team.

h2. Cluster configuration tests (Verify agents run on systems as configured)

h3. agents only, round robin test

table{border:1px solid black}.

|_.Purpose | Verify only agents run jobs using round robin load balancing|

|_.Dependencies | must be tested in a cluster w/at least 2 agent systems|

table{border:1px color:black}.

|_. Step |_.Action |_.Expected Results|

|1. | stop scheduler with /etc/init.d/fossology stop | scheduler should do a graceful shutdown |

|2. | edit [HOSTS] section of fossology.conf file to specify agents only | example:

griphook = griphook /usr/local/etc/fossology 10

pigwidgeon = pigwidgeon/usr/local/etc/fossology 10 |

|3. | edit /etc/init.d/fossology to increase log file verbosity  |  SCHEDULEROPT="--daemon --reset --verbose=952"   |

|4. | start scheduler with /etc/init.d/fossology start | scheduler should start in background with no errors or warnings in the log file (/var/log/fossology/fossology.log); log file start banner should indicate "verbose: 952" |

|5. | Start several jobs; a small upload with several analysis will do the trick  | observe and verify in the log file that jobs are started on agent systems +only+ in a round robin fashion

example:

@2012-02-07 12:41:25 scheduler [25509] :: Starting JOB[1].wget_agent

2012-02-07 12:41:25 scheduler [25509] :: HOST[griphook] load increased to 1@

...

@2012-02-07 12:50:59 scheduler [25509] :: Starting JOB[2].ununpack

2012-02-07 12:50:59 scheduler [25509] :: HOST[pigwidgeon] load increased to 1@

...

@2012-02-07 12:51:37 scheduler [25509] :: Starting JOB[3].adj2nest

2012-02-07 12:51:37 scheduler [25509] :: HOST[griphook] load increased to 1@

...

@2012-02-07 12:51:37 scheduler [25509] :: Starting JOB[4].copyright

2012-02-07 12:51:37 scheduler [25509] :: HOST[pigwidgeon] load increased to 1@

...

@2012-02-07 12:51:37 scheduler [25509] :: Starting JOB[5].nomos

2012-02-07 12:51:37 scheduler [25509] :: HOST[griphook] load increased to 1@

...

@2012-02-07 12:51:37 scheduler [25509] :: Starting JOB[6].pkgagent

2012-02-07 12:51:37 scheduler [25509] :: HOST[pigwidgeon] load increased to 2@  |

h2. Cluster functional tests 

h3. Upload from file

table{border:5px, color:black}.

|_.Purpose | Verify upload from file works in a cluster  |

|_.Dependencies |  must be tested in a cluster w/at least 1 agent system  |

table{border:1px solid black}.

|_. Step |_.Action |_.Expected Results|

|1. |Click on the top level "Upload" pull down menu & select "From File"  |UI should display "Upload a New File" page|

|2. |Complete steps 1-5 on the page, supplying a file on your local system; click the "Upload"  |page should refresh with message at the top indicating a job has started to upload your request with a link to view the job status |

|3. | click on the upload link for your job |UI should display "Show Jobs" page with your requested upload & 2 jobs: ununpack & adj2nest |

|4. | When all 2 jobs are completed, click the job # in the far left to view the log files for each |verify all 2 jobs ran without any fatal errors |

|5. | Return to the show jobs page and click on the upload name to browse | UI should display your upload in the "Browse" page|

h3. Upload a file using "Upload from URL"

table{border:5px, color:black}.

|_.Purpose | Verify a file can be uploaded using Upload from URL in a cluster  |

|_.Dependencies |  must be tested in a cluster w/at least 1 agent system  |

table{border:1px solid black}.

|_. Step |_.Action |_.Expected Results|

|1. | Click on the top level "Upload" pull down menu & select "Upload from URL"| UI should display "Upload from URL" page|

|2. | Complete steps 1-4 on the page, supplying a _valid_ URL to a _file_; click the "Upload!" button at the bottom of the page|page should refresh with message at the top indicating a job has started to upload your request with a link to view the job status|

|3. | click on the upload link for your job |UI should display "Show Jobs" page with your requested upload & 3 jobs: wget_agent, ununpack & adj2nest |

|4. | When all 3 jobs are completed, click the job # in the far left to view the log files for each |verify all 3 jobs ran without any fatal errors |

|5. | Return to the show jobs page and click on the upload name to browse | UI should display your upload in the "Browse" page|

h3. Upload a directory _and it's contents_ using "Upload from URL"

table{border:5px, color:black}.

|_.Purpose | Verify a directory and it's contents can be uploaded using Upload from URL in a cluster  |

|_.Dependencies |  must be tested in a cluster w/at least 1 agent system  |

table{border:1px solid black}.

|_. Step |_.Action |_.Expected Results|

|1. | Click on the top level "Upload" pull down menu & select "Upload from URL"| UI should display "Upload from URL" page|

|2. | Complete steps 1-4 on the page, supplying a _valid_ URL to a _directory_ containing at least 2 items; click the "Upload!" button at the bottom of the page|page should refresh with message at the top indicating a job has started to upload your request with a link to view the job status|

|3. | click on the upload link for your job |UI should display "Show Jobs" page with your requested upload & 3 jobs: wget_agent, ununpack & adj2nest |

|4. | When all 3 jobs are completed, click the job # in the far left to view the log files for each |verify all 3 jobs ran without any fatal errors |

|5. | Return to the show jobs page and click on the upload name to browse | UI should display your upload in the "Browse" page|

h3. "Upload from URL" works with wildcards

table{border:5px, color:black}.

|_.Purpose | Verify wildcards work with Upload from URL in a cluster  |

|_.Dependencies |  must be tested in a cluster w/at least 1 agent system  |

table{border:1px solid black}.

|_. Step |_.Action |_.Expected Results|

|1. | Click on the top level "Upload" pull down menu & select "Upload from URL"| UI should display "Upload from URL" page|

|2. | Complete steps 1-4, 5 and/or 6 on the page, supplying valid values for each; click the "Upload!" button at the bottom of the page|page should refresh with message at the top indicating a job has started to upload your request with a link to view the job status|

|3. | click on the upload link for your job |UI should display "Show Jobs" page with your requested upload & 3 jobs: wget_agent, ununpack & adj2nest |

|4. | When all 3 jobs are completed, click the job # in the far left to view the log files for each |verify all 3 jobs ran without any fatal errors |

|5. | Return to the show jobs page and click on the upload name to browse | UI should display your upload in the "Browse" page|

h3. Upload from server

table{border:5px, color:black}.

|_.Purpose | Verify upload from server works in a cluster  |

|_.Dependencies |  must be tested in a cluster w/at least 1 agent system  |

table{border:1px solid black}.

|_. Step |_.Action |_.Expected Results|

|1. |Click on the top level "Upload" pull down menu & select "From Server"  |UI should display "Upload from Server" page |

|2. |Complete steps 1-6 on the page, supplying the files or directory on the server; click the "Upload!" button at the bottom of the page  |page should refresh with message at the top indicating a job has started to upload your request with a link to view the job status |

|3. | click on the upload link for your job |UI should display "Show Jobs" page with your requested upload & 2 jobs: ununpack & adj2nest |

|4. | When all 2 jobs are completed, click the job # in the far left to view the log files for each |verify all 2 jobs ran without any fatal errors |

|5. | Return to the show jobs page and click on the upload name to browse | UI should display your upload in the "Browse" page|

h3. One-shot nomos

table{border:5px, color:black}.

|_.Purpose | Verify one-shot nomos works in a cluster  |

|_.Dependencies |  must be tested in a cluster w/at least 1 agent system  |

table{border:1px solid black}.

|_. Step |_.Action |_.Expected Results|

|1. |Click on the top level "Upload" pull down menu & select "One-Shot Analysis"  |UI should display "One-Shot License Analysis" page |

|2. |Select the file to Upload; and click the "Analyze!" button  |page should refresh with message at the top indicating license analysis result |

h3. One-shot copyright

table{border:5px, color:black}.

|_.Purpose | Verify one-shot copyright works in a cluster  |

|_.Dependencies |  must be tested in a cluster w/at least 1 agent system  |

table{border:1px solid black}.

|_. Step |_.Action |_.Expected Results|

|1. |Click on the top level "Upload" pull down menu & select "One-Shot Copyright/Email/URL"  |UI should display "One-Shot Copyright/Email/URL Analysis" page |

|2. |Select the file to Upload; and click the "Upload and scan" button  |page should refresh with message at the top indicating copyright/email/URL analysis result |