Slot Object
Slot – is an object, which represents local storage of tests.
Slot has following fields: name, path, branch. Also it contains information about login and password, if remote repository requires autentification.
Use-Cases
When “actions” are mentioned, things like check out, recheck out and update are meant.
Add Slot
When you adding a slot, you should fill up those fields:
- Name. It should be unique
- Path to the folder in which testing framework would be stored. You should have rights on writing there. Question: What if folders in differen slots are equel? Should we warn, or ask to change, or what?
- Branch.
- Authorization/ No authorization
- If authorization required – login and password.
Edit Slot
When you editing a slot, you may change those fields only if no action happening:
- Name. It should be unique.
- Branch.
I think, that we shouldn't allow user to change path in slot, because actually it becomes another slot with equal name. Actually I'm not sure about branch too, 'cause if we change it, what we should do with previous version? Overwrite it?
Update Slot
If slot had been succesfully checked out and all actions are finished you can update it.
Recheck out Slot
If slot has not been succesfully checked out and all actions are finished you can recheck out it
Delete Slot
If all actions on this slot are completed and branch for this slot is deleted you can delete it.
