Test Plan

Test Plan for RockStor

Functionality to test

Share details

1. Should show total size of the share, used space and free space
2. Should show the pool that the share belongs to
3. Should be able to create and delete snapshots
4. Should be able to create and delete Samba share
5. Should be able to create and delete snapshots
6. Should be able to resize the share
7. Should be able to delete the share

Shares

1. Should list all shares with their sizes
2. Should be able to create multiple shares in the same pool
3. Should be able to delete shares
4. Should have a link to Create Share page

Create Share

1. Should be able to select the pool
2. Should be able to specify the size in KB, MB, GB, TB
3. Should not allow two shares with the same name in the same pool
4. Should allow two shares with the same name in two different pools

Pool details

1. Should show the disks that belong to this pool
2. Should show size of the pool
3. Should be able to create a share
4. Should be able to delete the pool

Pools

1. Should list all pools with name, size and raid level
2. Should have a link to the Create Pool page
3. Should be able to delete a pool if it contains no shares
4. Should not be able to delete a pool if it contains at least one share

Create Pool

1. Should be able to create a pool
2. Should not allow two pools with the same name
3. Should be able to create a pool with Raid0, Raid1, and Raid10
4. Should verify that the user has selected at least the minimum number of disks for the raid level selected.
5. Should not display disks that are already in use in the selection dialog

Disks

1. Should show disks with size and pool that they belong to (if any)
2. Rescan should show new disks if new disks have been attached

Dashboard

1. Should show CPU Utilization, System Information and Smart Probes widgets
2. Should show widget selection dialog when widget configuration link is clicked

Services

1. Should be able to start and stop services.
2. The status icon should change when the service is started / stopped
3. Available actions should change when the status changes