autowebcompat
autowebcompat copied to clipboard
[WIP] adding crawler functions to testing
Work in progress for #75
@marco-c Sorry for delay! I was busy in exams. So, till now what I have done is creating a class for setting up the selenium drivers and provided a sample use of it though one test case. I would like to know if this is good method or there are some changes can be made to make it better. If it looks good then other possible functions can be added easily.
@marco-c Sorry for delay! I was busy in exams. So, till now what I have done is creating a class for setting up the selenium drivers and provided a sample use of it though one test case. I would like to know if this is good method or there are some changes can be made to make it better. If it looks good then other possible functions can be added easily.
Yes, the approach looks good to me overall!
Codecov Report
Merging #103 into master will not change coverage. The diff coverage is
n/a.
@@ Coverage Diff @@
## master #103 +/- ##
=======================================
Coverage 18.95% 18.95%
=======================================
Files 16 16
Lines 1931 1931
Branches 328 328
=======================================
Hits 366 366
Misses 1562 1562
Partials 3 3
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing dataPowered by Codecov. Last update 96348a2...fc30dbe. Read the comment docs.
@marco-c Also, can I break up the task of adding tests cases? So taking the changes done in PR as one part and rest is completed by creating issues or it should be better if it completes in one PR?
@marco-c Also, can I break up the task of adding tests cases? So taking the changes done in PR as one part and rest is completed by creating issues or it should be better if it completes in one PR?
Sure, please file an issue for anything that should be tested that is not covered in this PR.
@poush do you still intend to work on this?
Closing for lack of response. Feel free to reopen if you still intend to work on this in the future.
Please provide your feedback on this pull request here.
Privacy statement: We don't store any personal information such as your email address or name. We ask for GitHub authentication as an anonymous identifier to account for duplicate feedback entries and to see people specific preferences.
@marco-c can you please reopen it? I would like to continue on it.
Sure!
ping @poush
😅Got busy in my summer project. Give me a week or two. I will fix the travis issues.
@marco-c test seems passing, please have a look. I will put into the issue what next methods will be covered in next PR.
@marco-c Can you please check it again? I fixed all the reviews that same day.