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.

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

test runs - but no screenshots + various bumps on the way #50

Open
yonatanLehman opened this issue Sep 5, 2019 · 0 comments
Open

test runs - but no screenshots + various bumps on the way #50

yonatanLehman opened this issue Sep 5, 2019 · 0 comments

Comments

@yonatanLehman
Copy link

yonatanLehman commented Sep 5, 2019

Hi
First of all thanks for this great contribution to the universe.

I have tried to build and run the lambda-selenium-java example
and have met with various problems.

The current status is that when I do
gradle clean test the test runs
output in the bash says
5 actionable tasks: 5 executed
but the build/screenshots directory is empty

I'm running on windows10 using bash

Other problems I had on the way for others following in my path:

  1. In https://blackboard.github.io/lambda-selenium/java-tutorial.html it says to do
    git clone git@github.com:blackboard/lambda-selenium.git
    I got an error on this, changing it to the following fixed it
    git clone https://github.com/blackboard/lambda-selenium.git

  2. As already reported in another issue, I had to change a line in build.gradle to

    dependencies {
        classpath 'com.github.jengelman.gradle.plugins:shadow:5.1.0'
    }
  1. When I ran gradle clean unzipLibs shadowJar deploy, I got
> Task :deploy FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':deploy'.
> A problem occurred starting process 'command 'sls''
  1. running sls deploy directly in bash seems to work, but I got an error
    Error: ENOENT: no such file or directory, open 'C:\Users\User\Documents\EKB\testEKB\lambda-selenium\lambda-selenium-java2\lambda-selenium\lambda-selenium-java\build\libs\lambda-selenium-all.jar'

indeed the name of the file in that directory was lambda-selenium.jar (wihtout the -all) changing the name in serverless.yaml package: artifact solved this problem but...

  1. The test ran but I got null pointer errors in file ExampleTestService.java line 33
    TestResult testResult = testInvoker.run();

As I wild guess I created a function "lambda-selenium-function" using the aws console
and hey presto - it executed- but no screenshots..

How do I proceed from here?
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant