Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uitest #174

Open
wants to merge 63 commits into
base: ui
Choose a base branch
from
Open

Uitest #174

wants to merge 63 commits into from

Conversation

backtrack-5
Copy link

Added UI testing using selenium and python

gas1121 and others added 29 commits August 14, 2017 18:40
* Trivial tense/typos

* Update dmoz.org to dmoztools.net since dmoz.org now redirects. (istresearch#145) (istresearch#147)
docker eleasticsearch container not running when the vm.max_map_count has the default value which is too low.
* vm.max_map_count tip

docker eleasticsearch container not running when the vm.max_map_count has the default value which is too low.

* Ansible Kafka template consumer.properties.j2 had a hardcoded
zookeeper.connect value.

Now the value is created from the iteration of the zookeeper_host_list
(host and port).
Because of the wrong spider name, a wrong redis directory ended up containing the queue key.
This way the spider was not crawling the provided link.
This is a sneaky bug seen when you override the LogObject class `add_extras()` method, and then you would like to use the callback functionality with your newly returned values.

Before, the callback would only be passed the original extra parameter, now it is passed the updated parameters.
Hopefully this fixes the crawler integration tests which have been failing, tested locally and works
URL changed from istresearch.com to dmoztools.net for better stability
This should bring us up to speed with all the changes made via PR's or other minor issues
@backtrack-5 backtrack-5 mentioned this pull request Mar 29, 2018
@backtrack-5
Copy link
Author

Hi @madisonb @damienkilgannon , I tried rebase with DEV and commited my branch, Still travis-ci is failing. Not sure what is the issue :(.

@backtrack-5
Copy link
Author

Hi @damienkilgannon, @madisonb - I have pulled branch ui and added my test case. I am wondering, If i do a simple commit and check whether the ui branch is passing in travis-ci .

Please let me know your if that works.

@backtrack-5
Copy link
Author

Hi @damienkilgannon , Did you get a chance to look into it ?

@damienkilgannon
Copy link
Contributor

@sornalingam ... i believe @madisonb found an issue #175 which is likely related

@backtrack-5
Copy link
Author

Hi @damienkilgannon , Thanks for the update. I will wait for @madisonb response.

@damienkilgannon
Copy link
Contributor

@sornalingam so #175 is closed and merged into dev ... so if you could try merging that back into your branch to start and see does that resolve the failing build.

Sornalingam added 2 commits April 18, 2018 17:30
…into uitest

# Conflicts:
#	docs/topics/changelog.rst
#	requirements.txt
@coveralls
Copy link

Coverage Status

Coverage increased (+4.2%) to 65.96% when pulling 7307378 on sornalingam:uitest into 5a2bf12 on istresearch:ui.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage increased (+4.2%) to 65.96% when pulling 7307378 on sornalingam:uitest into 5a2bf12 on istresearch:ui.

@backtrack-5
Copy link
Author

backtrack-5 commented Apr 18, 2018

Hi @damienkilgannon @madisonb ,

I found the problem. Installing Chrome dependency is casing the issue in Tavis-ci build.Refer the latest build build#652

I have added the chrome dependency installation steps in docker and Dockerfile.py3 and it is working fine.

I am not sure how to add it in the Dockerfile.py2alpine, and env's centos and ubuntu from .travis.yml file

I will look into it and fix those issue. In the meantime if you know the solution please leave the comment.

Thanks,

@madisonb
Copy link
Collaborator

I don't have a further comment on how to fix the issue, other than we should have all tests passing in all environments before we merge stuff in.

Luckily, everything is container based and you should be able to work with things if you have the ability to get it working in Py3 land.

For ansible, you would add your installation commands to here. You can view the testing containers here.

For alpine, you probably just need to work with the alpine environment and install some extra dependencies in order to get Chrome to work. Think of it as a slim flavor of linux that needs extra packages installed to get stuff going, but makes super small container images.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants