QACOE-242: add Dockerfile and instructions how to use cypress with docker by GoranP · Pull Request #11 · ModusCreateOrg/qa-dept

GoranP · 2022-01-25T13:54:49Z

No description provided.

GoranP · 2022-01-25T14:53:43Z

@chan-chandra take a peek at this PR. I added Dockerfile and a few instructions for cypress. Please comment on what needs to be changed for this to be merged in the main repo.

pedrohyvo · 2022-01-25T16:32:50Z

@GoranP could you add your ticket number in the title and description of this PR, please.

e.g. QACOE-111: add Dockerfile...

GoranP · 2022-01-27T08:48:55Z

@chan-chandra @pedrohyvo
Could one of you guys please check if Nightwatch tests are OK on your system?

I could not successfully run them all - only partially. After .click(...) action, it seems there are no results or better there is no element called <.main-results> on the Ecosia website after. I tried various existing elements like #main but nothing helps.

I even injected logging and hitting ENTER like this but everything seems ok and I cannot find result element from website:
.setValue('input[type=search]', ['nightwatch testing framework',browser.Keys.ENTER], function(err){console.log(err)})

Following are errors I get:

============================================
ℹ Connected to localhost on port 9515 (126ms).
  Using: chrome (97.0.4692.99) on Linux platform.

✔ Running search for a keyword:

✔ Element <body> was visible after 23 milliseconds.
✔ Testing if the page title contains 'Ecosia' (7ms)
✔ Testing if element <input[type=search]> is visible (25ms)
✔ Testing if element <button[type=submit]> is visible (29ms)
   NoSuchElementError: An error occurred while running .getText() command on <.mainline-results>: 
   {"sessionId":"2deacfb1ac8afeb2db0d1871f07d5091","status":0,"value":[]}
       at processTicksAndRejections (node:internal/process/task_queues:96:5)
✖ Testing if element <.mainline-results> contains text 'Nightwatch.js' in 5000ms - expected "contains text 'Nightwatch.js'" but got: "element could not be located" (5424ms)
    at DescribeInstance.<anonymous> (/app/tests/DemoBDD.js:13:17)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) 


FAILED: 1 assertions failed, 1 errors and  4 passed (6.931s)

However - since I am trying that in Docker and using headless chrome that might be an issue.

Could you please execute that on your machine with all dependencies installed and with a headless option? Just to eliminate that this is a chrome headless problem and that issue is just my lack of knowledge of how Nightwatch access DOM objects on HTML result. :)

This is the config I am using for nigtwatch.js:

module.exports = {
  "src_folders" : ["tests/"],

  "webdriver" : {
    "start_process": true,
    "server_path": "node_modules/.bin/chromedriver",
    "port": 9515
  },

  "test_settings" : {
    "default" : {
      "desiredCapabilities": {
        "browserName": "chrome",
        "chromeOptions" : {
            "args" : ["headless", "no-sandbox", "disable-gpu"]
        }
      }
    },

    "chrome" : {
      "desiredCapabilities": {
        "browserName": "chrome",
        "chromeOptions" : {
            "args" : ["headless", "no-sandbox", "disable-gpu"]
        },
        "javascriptEnabled": true,
        "acceptSslCerts": true
      }
    } 
  },
}```

chan-chandra · 2022-01-27T14:11:06Z

@chan-chandra @pedrohyvo Could one of you guys please check if Nightwatch tests are OK on your system?

I could not successfully run them all - only partially. After .click(...) action, it seems there are no results or better there is no element called <.main-results> on the Ecosia website after. I tried various existing elements like #main but nothing helps.

I even injected logging and hitting ENTER like this but everything seems ok and I cannot find result element from website: .setValue('input[type=search]', ['nightwatch testing framework',browser.Keys.ENTER], function(err){console.log(err)})

Following are errors I get:
============================================
ℹ Connected to localhost on port 9515 (126ms).
  Using: chrome (97.0.4692.99) on Linux platform.

✔ Running search for a keyword:

✔ Element <body> was visible after 23 milliseconds.
✔ Testing if the page title contains 'Ecosia' (7ms)
✔ Testing if element <input[type=search]> is visible (25ms)
✔ Testing if element <button[type=submit]> is visible (29ms)
   NoSuchElementError: An error occurred while running .getText() command on <.mainline-results>: 
   {"sessionId":"2deacfb1ac8afeb2db0d1871f07d5091","status":0,"value":[]}
       at processTicksAndRejections (node:internal/process/task_queues:96:5)
✖ Testing if element <.mainline-results> contains text 'Nightwatch.js' in 5000ms - expected "contains text 'Nightwatch.js'" but got: "element could not be located" (5424ms)
    at DescribeInstance.<anonymous> (/app/tests/DemoBDD.js:13:17)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) 


FAILED: 1 assertions failed, 1 errors and  4 passed (6.931s)
However - since I am trying that in Docker and using headless chrome that might be an issue.

Could you please execute that on your machine with all dependencies installed and with a headless option? Just to eliminate that this is a chrome headless problem and that issue is just my lack of knowledge of how Nightwatch access DOM objects on HTML result. :)

This is the config I am using for nigtwatch.js:
module.exports = {
  "src_folders" : ["tests/"],

  "webdriver" : {
    "start_process": true,
    "server_path": "node_modules/.bin/chromedriver",
    "port": 9515
  },

  "test_settings" : {
    "default" : {
      "desiredCapabilities": {
        "browserName": "chrome",
        "chromeOptions" : {
            "args" : ["headless", "no-sandbox", "disable-gpu"]
        }
      }
    },

    "chrome" : {
      "desiredCapabilities": {
        "browserName": "chrome",
        "chromeOptions" : {
            "args" : ["headless", "no-sandbox", "disable-gpu"]
        },
        "javascriptEnabled": true,
        "acceptSslCerts": true
      }
    } 
  },
}```

@GoranP Its failing for headless mode, will update the code

GoranP · 2022-01-31T08:12:02Z

@chan-chandra OK thnx. To it is headless mode then. I tried a few variants but non worked - please notify me when you update the code for headless (if it is possible at all).

…ment example

into QACOE-242

GoranP · 2022-02-01T08:33:29Z

I pushed NightwatchJS Dockerfile and slightly adjusted nightwatch.js config file with headless support.
Also, brief documentation of building docker image pushing and deploying on Kubernetes is added in the readme file.
I hope that we can adjust the test code to support headless testing because right now half of the tests will fail with this configuration.
@chan-chandra @pedrohyvo

GoranP and others added 3 commits January 25, 2022 14:51

adding Dockerfile and instructions how to use cypress with docker

a650020

Fixing typos

597a7ec

Update README.MD

3810d98

GoranP changed the title ~~add Dockerfile and instructions how to use cypress with docker~~ QACOE-242: add Dockerfile and instructions how to use cypress with docker Jan 26, 2022

GoranP added 2 commits February 1, 2022 09:27

QACOE-242 add support for dockerised nightwatch and kubernetes deploy…

7e6a8b9

…ment example

Merge branch 'QACOE-242' of https://github.com/GoranP/qa-coe-experiments

357a875

into QACOE-242

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

QACOE-242: add Dockerfile and instructions how to use cypress with docker#11

QACOE-242: add Dockerfile and instructions how to use cypress with docker#11
GoranP wants to merge 5 commits intoModusCreateOrg:masterfrom
GoranP:QACOE-242

GoranP commented Jan 25, 2022

Uh oh!

GoranP commented Jan 25, 2022

Uh oh!

pedrohyvo commented Jan 25, 2022

Uh oh!

GoranP commented Jan 27, 2022 •

edited

Loading

Uh oh!

chan-chandra commented Jan 27, 2022 •

edited

Loading

Uh oh!

GoranP commented Jan 31, 2022

Uh oh!

GoranP commented Feb 1, 2022

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

GoranP commented Jan 25, 2022

Uh oh!

GoranP commented Jan 25, 2022

Uh oh!

pedrohyvo commented Jan 25, 2022

Uh oh!

GoranP commented Jan 27, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

chan-chandra commented Jan 27, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

GoranP commented Jan 31, 2022

Uh oh!

GoranP commented Feb 1, 2022

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

GoranP commented Jan 27, 2022 •

edited

Loading

chan-chandra commented Jan 27, 2022 •

edited

Loading