Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Peter Tesler
    @vptes1
    👍
    GameOSX
    @GameOSX
    hi, I've got a little problem with starting smashtest - i'm starting webdriver-manager in separate terminal and when i type smashtest i'm getting this error (windows 10)
    Open Chrome
    Error: Server terminated early with status 1   [D:/Workspace/SmashTest/helloworld.smash:1]
        at C:\Users\Lenovo\AppData\Roaming\npm\node_modules\smashtest\node_modules\selenium-webdriver\remote\index.js:251:52
        at processTicksAndRejections (internal/process/task_queues.js:93:5)
    Peter Tesler
    @vptes1
    Hi - Did you run the command as smashtest --test-server= http://localhost:4444/wd/hub ?
    Or add test-server to your smashtest.json config file?
    Peter Tesler
    @vptes1
    ^ @GameOSX
    GameOSX
    @GameOSX
    yes I tried both
    Peter Tesler
    @vptes1
    Please provide steps to reproduce, i.e., what you're passing in to the command line, what's in your config file (if it exists), what's in your .smash file(s), the output of webdriver-manager, etc.
    Just from googling that error, it seems like an internal webdriver thing. You can try reinstalling webdriver, or use a different option on https://smashtest.io/getting-started/setup
    See if that helps
    GameOSX
    @GameOSX

    ok so i've reinstalled webdriver-manager and smashtest - nothing changed. my starting command is

    smashtest --test-server=http://127.0.0.1:4444/wd/hub

    my helloworld.smash:

    Open Chrome
    
        Navigate to 'google.com'
    
            Type 'hello world[enter]' into 'textbox'

    and output form webdriver manager:

    webdriver-manager: using global installed version 12.1.7
    [10:58:26] I/start - java -Dwebdriver.gecko.driver=C:\Users\Lenovo\AppData\Roaming\npm\node_modules\webdriver-manager\selenium\geckodriver-v0.26.0.exe -Dwebdriver.chrome.driver=C:\Users\Lenovo\AppData\Roaming\npm\node_modules\webdriver-manager\selenium\chromedriver_78.0.3904.105.exe -jar C:\Users\Lenovo\AppData\Roaming\npm\node_modules\webdriver-manager\selenium\selenium-server-standalone-3.141.59.jar -port 4444
    [10:58:26] I/start - seleniumProcess.pid: 12056
    10:58:27.048 INFO [GridLauncherV3.parse] - Selenium server version: 3.141.59, revision: e82be7d358
    10:58:27.146 INFO [GridLauncherV3.lambda$buildLaunchers$3] - Launching a standalone Selenium Server on port 4444
    2019-12-05 10:58:27.195:INFO::main: Logging initialized @377ms to org.seleniumhq.jetty9.util.log.StdErrLog
    10:58:27.417 INFO [WebDriverServlet.<init>] - Initialising WebDriverServlet
    10:58:28.011 INFO [SeleniumServer.boot] - Selenium Server is up and running on port 4444

    so it looks like nothing is even trying to start chromedriver on selenium server.
    I've also tried all other setups - nothing is working for me :/
    Even if I'm trying to start Firefox - the same error.

    Peter Tesler
    @vptes1
    Have you tried running webdriver-manager update? How about using https://www.npmjs.com/package/selenium-standalone instead of webdriver-manager?
    What versions of chrome and node are you using?
    Peter Tesler
    @vptes1
    Also, if you're using a webdriver manager, you shouldn't set the SELENIUM_SERVER_JAR env variable, if you're doing that
    That's all I can think of atm
    GameOSX
    @GameOSX
    wow - selenium-standalone helped and now it's working :) thx @vptes1 for your help
    Peter Tesler
    @vptes1
    Good to hear!
    id7digital
    @id7digital
    hi guys, im having a bit of trouble with the command line smashtest arguments, --recursive does not seem to pick up any functions in subfolders in my directory
    smashtest folderpath/*.smash --recursive
    Peter Tesler
    @vptes1
    @id7digital Try running just smashtest --recursive (possibly also cding into folderpath)
    I believe --recursive overrides the path passed into the command
    Peter Tesler
    @vptes1
    Everyone, I've updated https://smashtest.io/getting-started/setup to recommend using selenium-standalone for windows users (as opposed to webdriver-manager). It seems that a number of you had trouble using webdriver-manager on windows, even though that's the most popular manager on npm. If you've had success with webdriver-manager, or trouble with selenium-standalone, please let me know. I'd love to get your feedback and update the site accordingly.
    id7digital
    @id7digital
    thanks @vptes1
    Craig Waite
    @craigvl
    yes selenium-standalone seems to work well on windows
    Notice that your doco states that you need to download the drivers , I think that standalone does this for you?
    Peter Tesler
    @vptes1
    Yes, it says you need to download the drivers if you're doing option 1, the manual install of selenium standalone.
    Selenium standalone, not the npm package selenium-standalone
    Option 2 is the manager option (npm package webdriver-manager or selenium-standalone)
    Craig Waite
    @craigvl
    Whoops read option 1 as the NPM package :0)
    Robby Tarigan
    @robbytarigan
    Hi. Does anyone know why smashtest gives error like "Error: Server was killed with SIGTERM"?
    That is using smashtest 1.6.9 and node 12.13.1 on windows. Example of log:
    Error
    Error: Server was killed with SIGTERM [C:/projects/project1/main.smash:2]
    at C:\projects\project1\node_modules\selenium-webdriver\remote\index.js:251:52
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    Peter Tesler
    @vptes1
    What's in your test? What browser is this happening in? Are you using a --test-server? (if not, did you set the SELENIUM_SERVER_JAR as per https://smashtest.io/getting-started/setup ?)
    Also, it's a good idea to upgrade smashtest to the latest version
    Peter Tesler
    @vptes1
    The whole SIGTERM thing is an error internal to selenium
    Craig Waite
    @craigvl
    Needing to catch the UnexpectedAlertOpenError exception that gets thrown in selenium-webdriver error.js (592) , just wondering where this should be caught to make sure that I am doing this correctly, Thanks.
    Peter Tesler
    @vptes1
    I assume you're getting that because an alert is open and you're trying to do something else? Is the alert supposed to be there in the first place?
    Craig Waite
    @craigvl
    Yes the application that I am testing is using alerts for user actions "Are you sure you want to delete this" etc..
    Peter Tesler
    @vptes1
    Then you have to close the alert first, then do stuff
    there are a few steps that do that
    i.e., click one of the buttons in the alert
    or alternatively you can use js in a code block
    Craig Waite
    @craigvl
    ok yes but the test just fails as soon as the alert is shown
    image.png
    Peter Tesler
    @vptes1
    Is clicking deleteButton what triggers the alert to open?
    And if so, what's the whole stack trace on that?
    Craig Waite
    @craigvl
    yes when you click on deleteButton and stack is:
      (Session info: chrome=78.0.3904.108)
      (Driver info: chromedriver=2.43.600210 (68dcf5eebde37173d4027fa8635e332711d2874a),platform=Windows NT 10.0.18362 x86_64)
        at Object.checkLegacyResponse (smashtest\node_modules\selenium-webdriver\lib\error.js:593:13)
        at parseHttpResponse (smashtest\node_modules\selenium-webdriver\lib\http.js:554:13)
        at Executor.execute (smashtest\node_modules\selenium-webdriver\lib\http.js:489:26)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    Peter Tesler
    @vptes1
    Did a google and in the first result they say how there's a bug in selenium where it throws that error if an alert is open and a screenshot is taken. Do you have screenshots on? If so, does disabling them (temporarily) fix this?
    Peter Tesler
    @vptes1
    Also, according to http://garajeando.blogspot.com/2014/06/protractor-how-to-avoid.html if you immediately dismiss the alert right after the click, it should make the problem go away. Not sure why this would work but they say it does haha
    Try using built-in steps Accept alert or Dismiss alert
    DWTUTS
    @dwtuts
    Hey is there a way to set return responses from API tests as a variable to use in another API test?
    Peter Tesler
    @vptes1
    You can return anything in a code block and then use the js variable prev to access it in a subsequent code block