Open snvc00 opened 3 years ago
When you are trying to create any source and you don't fill all the required fields. It can show this message in red:
When you are trying to login with wrong credentials, this message appears:
Please enter a correct email address and password. Note that both fields may be case-sensitive.
When you request access by selecting a product and introducing your e-mail, this message appears:
The first time you enter your mail. (Red PopUp )
Failed on request access. Error (Errno-5) No address associated with hostname
The second (n) time you enter your mail. (Yellow PopUp)
Error, User Already exist, you don't be activate yet.
In both scenarios, you don't get an email message.
When you are trying to create a new Product and you type an existing name product it shows:
Product name already exists.
If you are trying to create a new Keyword and you don't put a command in the drag and drop zone, you can't create it, and it does not appear a message about what is missing.
If you are trying to create a new Test Case and you don't put a command or a keyword in the drag and drop zone, you can't create it, and it does not appear a message about what is missing.
If you are trying to create a new Test Suite and you don't put a Test Case in the drag and drop zone, you can't create it, and it does not appear a message about what is missing.
If you try to extract an invalid url (html), you can see this error in the /home page.
<class 'urllib.error.HTTPError'>([])
(Adding documentation)
When you request access by selecting a product and introducing your e-mail, this message appears:
The first time you enter your mail. (Red PopUp):
Failed on request access. Error (Errno-5) No address associated with hostname
Change to :
Failed on request access. Error duplicate key value violates unique
constraint "users_pkey" DETAIL: Key(id)=(n)already exists
The second (n) time you enter your mail. (Yellow PopUp)
Error, User Already exist, you don't be activate yet.
In anyone of the scenarios, you don't get an email message.
(Adding more documentation)
If you are editing a TestCase and you don't specify the phase, you get this error (popUp on red):
{'phase':["This field may not be null."]}
When you are trying to create a new profile and you don't put a profile name you get this (popUp on red):
Name: This field may not be blank
When you are trying to edit the parameter, you need to set a name, otherwise you will get "This field is required" error.
When you are trying to edit the template and you don't put a name you get this (popUp on red):
Name: This field may not be blank
If you are trying to make a command and you don't specify the name or the source, you get this message (yellow popUp):
Name and Source are required
Even when you put those data correct, you can't make a command, and it does not appear something to tell you what it is wrong.
When you are trying to create or edit the robot framework version, you need to set the version and the zip file, otherwise you will get "This field is required" error.
If I try to extract robot commands from a .rar file, in the main window appears (on red):
Extract commands from robot Completed
Execution Failed
Error Detail:
File is not a zip file
When you are trying to create or edit a product, you need to set the product name and version, otherwise you will get "This field is required" error.
When you are trying to create or edit a library, you need to set the library name and version, otherwise you will get "This field is required" error.
If you want to create a library and you add any file with the "HML file" button, it would accept it. It doesn't appear any kind of message telling that it was an error, and it seems that the "creating the librery" worked like that.
When you are trying to create or edit a phase, you need to set the phase name and product, otherwise you will get "This field is required" error.
When you are trying to create an user, you need to set all the required fields (email, product, role, password and confirm password), otherwise you will get "This field is required" error.
Research and create technical documentation of common errors and functions susceptible to fail in the tool.