Build: #240 was successful
Job: Test, build and push docker image was successful
Test results
- 340 tests in total
- 21 seconds taken in total.
The following 340 tests have passed:
Show all tests on one pageStatus | Test | Duration |
---|---|---|
Test suite for single dictionary concepts should handle EDIT_CONCEPT_REMOVE_ONE_NAME
Test suite for single dictionary concepts should handle EDIT_CONCEPT_REMOVE_ONE_NAME
|
< 1 sec | |
Test suite for single dictionary concepts should handle FETCH_EXISTING_CONCEPT
Test suite for single dictionary concepts should handle FETCH_EXISTING_CONCEPT
|
< 1 sec | |
Test suite for single dictionary concepts should handle FETCH_EXISTING_CONCEPT_ERROR
Test suite for single dictionary concepts should handle FETCH_EXISTING_CONCEPT_ERROR
|
< 1 sec | |
Test suite for single dictionary concepts should handle FETCH_NEXT_CONCEPT
Test suite for single dictionary concepts should handle FETCH_NEXT_CONCEPT
|
< 1 sec | |
Test suite for single dictionary concepts should handle REMOVE_CONCEPT
Test suite for single dictionary concepts should handle REMOVE_CONCEPT
|
< 1 sec | |
Test suite for single dictionary concepts should handle REMOVE_ONE_ANSWER_MAPPING
Test suite for single dictionary concepts should handle REMOVE_ONE_ANSWER_MAPPING
|
< 1 sec | |
Test suite for single dictionary concepts should handle REMOVE_ONE_DESCRIPTION
Test suite for single dictionary concepts should handle REMOVE_ONE_DESCRIPTION
|
< 1 sec | |
Test suite for single dictionary concepts should handle REMOVE_ONE_NAME
Test suite for single dictionary concepts should handle REMOVE_ONE_NAME
|
< 1 sec | |
Test suite for single dictionary concepts should handle TOTAL_CONCEPT_COUNT
Test suite for single dictionary concepts should handle TOTAL_CONCEPT_COUNT
|
< 1 sec | |
Test suite for single dictionary concepts should handle search filtering by class
Test suite for single dictionary concepts should handle search filtering by class
|
< 1 sec | |
Test suite for single dictionary concepts should handle search filtering by source
Test suite for single dictionary concepts should handle search filtering by source
|
< 1 sec | |
Test suite for single dictionary concepts should handle sidebar items
Test suite for single dictionary concepts should handle sidebar items
|
< 1 sec | |
Test suite for single dictionary concepts should not change state if no action passed
Test suite for single dictionary concepts should not change state if no action passed
|
< 1 sec | |
Test suite for single dictionary concepts should respond with the correct payload
Test suite for single dictionary concepts should respond with the correct payload
|
< 1 sec | |
Test suite for sources actions dispatches ADD_EXISTING_CONCEPTS action type on respose from server
Test suite for sources actions dispatches ADD_EXISTING_CONCEPTS action type on respose from server
|
< 1 sec | |
Test suite for sources actions should return a success message after adding concepts
Test suite for sources actions should return a success message after adding concepts
|
< 1 sec | |
Test suite for sources actions should return an error message from the db when add an already added concept
Test suite for sources actions should return an error message from the db when add an already added concept
|
< 1 sec | |
Test suite for specific concepts actions should return an array of concepts
Test suite for specific concepts actions should return an array of concepts
|
< 1 sec | |
Test suite for specific concepts actions should return an array of concepts when ownerType is organization
Test suite for specific concepts actions should return an array of concepts when ownerType is organization
|
< 1 sec | |
Test suite for specific concepts actions should return an error message from the db
Test suite for specific concepts actions should return an error message from the db
|
< 1 sec | |
Test suite for user dashboard actions should dispatch USER_IS_MEMBER
Test suite for user dashboard actions should dispatch USER_IS_MEMBER
|
< 1 sec | |
Test suite for user dashboard actions should dispatch USER_IS_NOT_MEMBER
Test suite for user dashboard actions should dispatch USER_IS_NOT_MEMBER
|
< 1 sec | |
Test suite for user dashboard actions should handle CLEAR_DICTIONARY
Test suite for user dashboard actions should handle CLEAR_DICTIONARY
|
< 1 sec | |
Test suite for user dashboard actions should handle FETCH_USER_DICTIONARY
Test suite for user dashboard actions should handle FETCH_USER_DICTIONARY
|
< 1 sec | |
Test suite for user dashboard actions should handle FETCH_USER_ORGANIZATION
Test suite for user dashboard actions should handle FETCH_USER_ORGANIZATION
|
< 1 sec | |
Test suite for user dashboard actions should handle GET_USER
Test suite for user dashboard actions should handle GET_USER
|
< 1 sec | |
Test suite for user dashboard actions should handle error in FETCH_USER_DICTIONARY
Test suite for user dashboard actions should handle error in FETCH_USER_DICTIONARY
|
< 1 sec | |
Test suite for user dashboard actions should handle error in FETCH_USER_ORGANIZATION
Test suite for user dashboard actions should handle error in FETCH_USER_ORGANIZATION
|
< 1 sec | |
Test suite for user dashboard actions should handle error in GET_USER
Test suite for user dashboard actions should handle error in GET_USER
|
< 1 sec | |
Test suite for user dashboard actions should handle fetchUserData
Test suite for user dashboard actions should handle fetchUserData
|
< 1 sec | |
Test suite for user dashboard reducer should handle CLEAR_DICTIONARY
Test suite for user dashboard reducer should handle CLEAR_DICTIONARY
|
< 1 sec | |
Test suite for user dashboard reducer should handle FETCH_USER_DICTIONARY
Test suite for user dashboard reducer should handle FETCH_USER_DICTIONARY
|
< 1 sec | |
Test suite for user dashboard reducer should handle FETCH_USER_ORGANIZATION
Test suite for user dashboard reducer should handle FETCH_USER_ORGANIZATION
|
< 1 sec | |
Test suite for user dashboard reducer should handle GET_USER
Test suite for user dashboard reducer should handle GET_USER
|
< 1 sec | |
Test suite for user dashboard reducer should handle IS_FETCHING
Test suite for user dashboard reducer should handle IS_FETCHING
|
< 1 sec | |
Test suite for user dashboard reducer should handle USER_IS_MEMBER
Test suite for user dashboard reducer should handle USER_IS_MEMBER
|
< 1 sec | |
Test suite for user dashboard reducer should handle USER_IS_NOT_MEMBER
Test suite for user dashboard reducer should handle USER_IS_NOT_MEMBER
|
< 1 sec | |
Test suite for user dashboard reducer should not change state if no action passed
Test suite for user dashboard reducer should not change state if no action passed
|
< 1 sec | |
Test suite for vote reducer should handle FETCHING_ORGANIZATIONS
Test suite for vote reducer should handle FETCHING_ORGANIZATIONS
|
< 1 sec | |
Test suite for vote reducer should handle FETCH_CIEL_CONCEPTS
Test suite for vote reducer should handle FETCH_CIEL_CONCEPTS
|
< 1 sec | |
Test suite for vote reducer should handle IS_FETCHING
Test suite for vote reducer should handle IS_FETCHING
|
< 1 sec | |
Test suite for vote reducer should return the initial state
Test suite for vote reducer should return the initial state
|
< 1 sec | |
Testing Edit concept actions should handle CLEAR_PREVIOUS_CONCEPT
Testing Edit concept actions should handle CLEAR_PREVIOUS_CONCEPT
|
< 1 sec | |
Testing Edit concept actions should handle EDIT_CONCEPT_ADD_DESCRIPTION
Testing Edit concept actions should handle EDIT_CONCEPT_ADD_DESCRIPTION
|
< 1 sec | |
Testing Edit concept actions should handle EDIT_CONCEPT_CREATE_NEW_NAMES
Testing Edit concept actions should handle EDIT_CONCEPT_CREATE_NEW_NAMES
|
< 1 sec | |
Testing Edit concept actions should handle EDIT_CONCEPT_REMOVE_ONE_DESCRIPTION
Testing Edit concept actions should handle EDIT_CONCEPT_REMOVE_ONE_DESCRIPTION
|
< 1 sec | |
Testing Edit concept actions should handle EDIT_CONCEPT_REMOVE_ONE_NAME
Testing Edit concept actions should handle EDIT_CONCEPT_REMOVE_ONE_NAME
|
< 1 sec | |
Testing Edit concept actions should handle FETCH_EXISTING_CONCEPT
Testing Edit concept actions should handle FETCH_EXISTING_CONCEPT
|
< 1 sec | |
Testing Edit concept actions should handle UPDATE_CONCEPT
Testing Edit concept actions should handle UPDATE_CONCEPT
|
< 1 sec | |
Testing Edit concept actions should handle error in FETCH_EXISTING_CONCEPT_ERROR for fetching exing concepts
Testing Edit concept actions should handle error in FETCH_EXISTING_CONCEPT_ERROR for fetching exing concepts
|
< 1 sec |