2022-01-17 15:26:36 +00:00
|
|
|
Feature: The Replay API client
|
2022-01-14 13:27:34 +00:00
|
|
|
|
|
|
|
Scenario: Testing every environment variable getter
|
|
|
|
Given the Replay client
|
|
|
|
When each one of the getters is called
|
2022-01-17 15:26:36 +00:00
|
|
|
Then all of the returns must be either of the type string or the type None
|
|
|
|
|
|
|
|
|
|
|
|
Scenario: Testing the process of creating and registering a Log
|
|
|
|
Given the Replay client
|
|
|
|
And a Log created
|
|
|
|
When the log method is called
|
2022-01-18 11:29:19 +00:00
|
|
|
Then this new log must be registered in the Replay Data Base
|
|
|
|
|
|
|
|
|
|
|
|
# Since this is a remote repository, it is impossible to test the config getters methods.
|
2022-01-18 14:30:58 +00:00
|
|
|
# They have to be runned inside a local repository wich contains Replay, so, unfortunatelly, they will not be tested, at least not for now.
|
|
|
|
|
|
|
|
|
|
|
|
#It is also not possible to test the open_app method for the same reasons as above.
|
|
|
|
|
|
|
|
|
|
|
|
Scenario: Testing the menu_get_all_enabled method.
|
|
|
|
Given the Replay client
|
|
|
|
When the menu_get_all_enabled method is called
|
|
|
|
Then there must be a list as a return
|
|
|
|
|
|
|
|
|
|
|
|
# Given the fact that the methods "service_stop_all" and "exit" will break the tests chain, they cannot be tested.
|