Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
P
pubsweet-starter
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • pubsweet
  • pubsweet-starter
  • Issues
  • #3

Closed
Open
Opened Aug 15, 2017 by Sam Galson@g-sam
  • Report abuse
  • New issue
Report abuse New issue

e2e tests

Couple of things:

  1. End-to-end tests are buried inside a file in a directory called helpers in pubsweet-cli. These tests should be more discoverable. I raise the issue here because I suggest moving them to a folder in this repo, where the functionality under test might be clearer.

  2. Is Nightmare adequate? You cannot do cross-browser testing, unlike with Selenium. Will be easier to switch sooner rather than later...

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: pubsweet/pubsweet-starter#3