cadasta / cadasta-test Goto Github PK

We need to add test cases for changes that will be introduced by Cadasta/cadasta-platform#1786

PR Cadasta/cadasta-platform#1934

Some clicks are being triggered before the page is fully loaded, thus leaving the test stuck on the previous page.

#B27: Anonymous user can only see public projects on the projects lists

I would like to be able to narrow down which tests are run each time so that I have the option of running All, Category (i.e. accounts) or Specific Test (i.e. PasswordReset) rather than having to fun all of them every time.

#U10: PM can update the project name case
#U11: PM can update project without a name change

This is a follow-up after Cadasta/cadasta-platform#1842 was fixed.

We need to add test cases to the suite for changes introduced in Cadasta/cadasta-platform#1721

Every time you run the tests, it creates a new organization and a new project that are not removed at the end of the tests. If you have to run the tests multiple times, it really clutters up the database, which isn't a huge issue for local envs, but might be more of an issue for running it against staging if we plan on doing that.

#M13: Org admin can add a member by email address
#M14: Org admin can add a member by phone number

This is a follow-up after the phone login feature was implemented.

... as outlined in #48.

#B5: Project member can view project data

Note: Imports test cases can be tested using dev VM. (Exports test cases cannot be easily implemented because of lack of access to backend infrastructure.)

#B29: Project member can interact with the project map
#B30: Public user cannot interact with the project map
#B31: Anonymous user cannot interact with the project map

These test cases require map interaction/inspection for the site dashboard or locations page map.

#B8: Org member can see all org projects on the site dashboard
#B9: Non-org member can only see public projects on the site dashboard
#B28: Anonymous member can only see public projects on the site dashboard

These test cases require map interaction/inspection for the site dashboard map.

Functional tests intermittently stop running, without any error or explicit termination. I've seen this both on Travis builds and locally.

Examples:

.tox/py35-functional-batch3/lib/python3.5/site-packages/cadasta/test/record_tests/test_tenure_relationship_creation.py::TestTenureRelationshipCreation::test_user_can_create_custom_rel_with_new_conditional_individual 
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received
The build has been terminated

.tox/py35-functional-batch2/lib/python3.5/site-packages/cadasta/test/project_tests/test_browsing.py::TestBrowsing::test_org_member_can_see_all_org_projects_on_projects_lists 
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received
The build has been terminated

Some Search test cases can be implemented even without the Elasticsearch infrastructure such as the following:

#S8: Search bar pops up when clicking the search tab
#S9: Nothing pops up when clicking the search tab on the search page
#S10: Sidebar search bar is activated by clicking the search button
#S11: Sidebar search bar is activated by pressing the return key

#U5: Project extent can be modified
#U6: Project extent can be replaced

These test cases require map interaction/inspection for the project extent map.

#U6: Org admin can update the organization name case
#U7: Org admin can update organization without a name change

This is a follow-up after Cadasta/cadasta-platform#1842 was fixed.

#B6: Public user cannot view project data

Note: The test script assumes that the public user cannot view the Data, Parties, and Resources list pages since the project sidebar is missing. Currently, the user can go to these pages by modifying the URL but cannot actually view individual locations, parties, or resources.

Steps to reproduce the error

One test randomly fails on Travis builds. This only affects builds on the master branch, builds for PRs consistently pass.

• Passing build: https://www.travis-ci.org/Cadasta/cadasta-platform/builds/292064914
• Failing build: https://www.travis-ci.org/Cadasta/cadasta-platform/builds/292038573

Actual behavior

The tests fail.

Expected behavior

The tests should pass.

This is more of a question: Since the Cadasta Platform is set-up for python3, my dev environment has python3 set as the default. I ran into several conflicts because these tests were looking for files in the python2 directory that existed in the python3 directory. Maybe it would make sense to have a python3 branch so that we have the option of both?

Certain elements are out of view at different screen sizes. To prevent conflicts when switching from screen size to screen size, we should run set_window_size at the beginning of each test for consistency.

This includes changing roles of org members from one role to another and checking that the user has indeed been granted/revoked permissions. Or we can just check that the updated roles are reflected in project member lists and assume that their indicated role does have the correct permissions as tested by other existing implemented test cases (e.g., only project manager can upload questionnaire, or only data collector can create records, or only project user can view records).

All documentation is outdated. Both the README of this repository and the corresponding wiki pages don't reflect the recent changes.

Pages the need updates include:

• README
• Running functional tests
• Writing functional tests

Difficult to reproduce:

organization_tests/test_creation.py::TestCreation::test_duplicate_name_is_rejected fails intermittantly.

We discussed the issue in a call, @seav has a possible solution.

#LU1: User can modify location geometry
#LU2: User can replace location geometry

These test cases require map interaction for the site location map.