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.

Sign up for GitHub

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

Jump to bottom

Knowledge sharing for writing browser tests - with Protractor, to run in Sauce Labs, good docs and examples, etc #141

Open
cfarm opened this issue Sep 26, 2017 · 1 comment
Open

Knowledge sharing for writing browser tests - with Protractor, to run in Sauce Labs, good docs and examples, etc #141

cfarm opened this issue Sep 26, 2017 · 1 comment
Assignees
@mistergone
Labels
high-priority medium effort
Projects
FEWD task board

Comments

@cfarm
Copy link
Contributor

cfarm commented Sep 26, 2017

No description provided.

@cfarm cfarm created this issue from a note in FEWD task board (Make browser testing an automated process. Make manual browser testing easy. ) Sep 26, 2017
@cfarm cfarm changed the title Knowledge sharing for writing browser tests - with Protractor, to run in Sauce Labs, good docs and examples, etc - H Knowledge sharing for writing browser tests - with Protractor, to run in Sauce Labs, good docs and examples, etc Sep 26, 2017
@Scotchester
Copy link
Contributor

I need probably two more full walk-throughs of the browser (acceptance) testing setup before I will understand it fully :)

The big questions in my head:

  1. How are the files & directories structured? I.e., how do all the pieces fit together?
  2. What base concepts and principles do I need to have down cold if I need to write a new test and there isn't an obvious example to model it off of?

@cfarm cfarm moved this from Make browser testing an automated process. Make manual browser testing easy. to Backlog in FEWD task board Feb 26, 2019
@mistergone mistergone moved this from Backlog to Working in FEWD task board Feb 28, 2019
@mistergone mistergone self-assigned this Feb 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mistergone mistergone

Labels
high-priority medium effort
Projects
FEWD task board
  
Working
Milestone
No milestone
Development

No branches or pull requests
3 participants
@cfarm @Scotchester @mistergone