As ReactJS is overpowering AngularJS as the go-to framework for front end development, testers tend to find the best tool which suits all of their needs in the javascript world.

Join this talk to learn about "Why and How to use the Power of NightWatch" as compared to other existing popular automation frameworks in the testing industry today such as Protractor, CasperJS :

  • how NightWatch makes test code highly transparent and readable
  • how NightWatch adds layer of abstraction separating the HTML selectors from the page objects, thus, enabling reuse and promoting general tidiness in comparison to other testing tools
  • how running tests against specific browsers/environments in parallel is relatively easy with NightWatch
  • how it solves the problem of tests re-write (say login for use in multiple cases)
  • how you can extend/enhance your tests using custom commands, custom assertions and custom reporters
  • how you can automate mobile apps integrating NightWatch with Appium
 
 

Outline/Structure of the Talk

The session will cover the following aspects:

  • The power of Nightwatch.js
  • How you can incorporate POM in your tests
  • How you can run tests against specific browsers/environments in parallel
  • How you can begin to automate mobile browser tests using Nightwatch with Appium

Learning Outcome

Learning from my experiments (what worked, or didn’t)

  • How to kick-start writing tests using Javascript
  • How to make efficient use of configurations in nightwatch
  • How to extend framework to implement your application specific commands and assertions.
  • How to write readable, maintainable and reusable tests with PageObject model using nightwatch

Target Audience

Developers, Testers, Test Managers

Prerequisites for Attendees

Anyone who has basic knowledge of Selenium and beginner level knowledge of node.js and javascript.

schedule Submitted 1 year ago

Public Feedback

comment Suggest improvements to the Speaker
  • Pooja Shah
    By Pooja Shah  ~  1 year ago
    reply Reply

    Wow! the title grabs all my attention. Thoughtful Smriti, thanks for the submission. I see a great possibility here for a useful, interesting talk.

    Does it start with what NightWatch is or you also plan to start with having a comparison with existing popular setups people are already using more and struggling with specific problems, is this something attendees are going to take away too? Just an ideology, as a user, I get more attracted to migrate to something totally new when my existing system is a pain and the new has answers to them. If yes, including that in the proposal makes it more important to attend to from attendees point of view.

     

     

     

    • Smriti Tuteja
      By Smriti Tuteja  ~  1 year ago
      reply Reply

      Thanks for the comments Pooja!

      Yes, we do plan on having a comparison with other popular tools in testing industry today such as Protractor, CasperJS, WebdriverIO. Some points used for comparison would be:

      • How NightWatch makes test code highly transparent and readable.
      • How NightWatch adds layer of abstraction separating the HTML selectors from the page objects, thus, enabling reuse and promoting general tidiness in comparison to other testing tools
      • How you can handle commands and page object commands separately
      • How you can automate mobile apps integrating NightWatch with Appium as compared to Protractor

      We will update the proposal accordingly!

      • Pooja Shah
        By Pooja Shah  ~  1 year ago
        reply Reply

        Thanks Smriti for responding.

        Yes, starting with the problem set sounds good here. Just having 1-2 liner should do because everybody wants to solve the real problems. Having a mention of them in abstract's beginning can invite more relating and interesting attendees because I see possibilities of good discussions here. 

         

        • Smriti Tuteja
          By Smriti Tuteja  ~  1 year ago
          reply Reply

          Updated proposal's abstract accordingly.
          Thank You!


  • Liked Sanjay Kumar
    keyboard_arrow_down

    Sanjay Kumar - ChroPath - a smarter way to get locators and verify them.

    Sanjay Kumar
    Sanjay Kumar
    ChroPath Creator
    InMobi
    schedule 1 year ago
    Sold Out!
    20 Mins
    Talk
    Beginner

    still writing relative xpath manually ?

    Do you want to save 20-30% time of automation script writing ?

    Feeling frustrated while writing unique locators ?

    looking for firepath replacement ?

  • Liked Smriti Tuteja
    keyboard_arrow_down

    Smriti Tuteja / Shirish Padalkar - Journey from Callback to Promises to Async/Await

    45 Mins
    Talk
    Intermediate

    In this world of asynchronicity, where it is easy to build applications using single page application frameworks, people struggle at the writing functional tests for such applications.

    Understanding this asynchronous nature of newer tools and frameworks needs efforts. In this talk we will talk about our journey from writing test with callback (hell) to using Promises and finally achieving nirvana with the power of async/await in JavaScript.

    This is a time travel of asynchronous programming and where does the future lie. The discussion will include:

    • Callbacks and their nested nature
    • Removing callbacks with Promises
    • And migrating to async/await


  • Liked Smriti Tuteja
    keyboard_arrow_down

    Smriti Tuteja - Migrate to Headless Chrome with Protractor

    Smriti Tuteja
    Smriti Tuteja
    Sr. Consultant
    Thoughtworks
    schedule 1 year ago
    Sold Out!
    20 Mins
    Experience Report
    Intermediate

    In this era of automation where everyone is focused on Agile and DevOps, learn how you can migrate from xvfb (X virtual framebuffer which enabled you to run browser tests without a display on a CI server) to Headless Chrome while you use Protractor.
    Attend this talk to understand how I migrated to headless chrome and the pain points. The discussion will include:

    • things you can take care of when migrating
    • checking versions compatibility for migration
    • things you will need to fix