-
Notifications
You must be signed in to change notification settings - Fork 54
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
Migrate s3auth-rest integration tests to CasperJS #200
Comments
I'm aware of the task, give me some time to find a developer... |
thank you for the ticket reported, I topped your account for 15 mins, transaction |
@caarlos0 the task is yours, please go ahead |
@carlosmiranda does this still make sense? The issue you refer is now closed... |
@caarlos0 you're working with this issue for 10 days already |
@caarlos0 this task is not yours any more (took too long), please stop. I'll give you something else |
@wentwog this task is yours, please help (see our key principles of work). If you have any technical questions, don't hesitate to ask right here Task's budget is 30 mins (see this for explanation) |
@wentwog you're holding this ticket for 8 days already. If it's not finished (and closed) in the next 40 hours, it will be re-assigned to someone else, see No Obligations principle... -5 added to your rating, at the moment it is: +25 |
@davvd I understand. Sorry. Better give this task to someone else since I feel I won't be able to meet the deadline. |
…rsHomePage test added
…up casperjs directory
@carlosmiranda @davvd I've created a PR #246, Casperjs tests work, but there is an exception when a test tries to check home page: com.amazonaws.AmazonServiceException: Status Code: 400, AWS Service: AmazonDynamoDBv2, AWS Request ID: 0Q9H7PJ91G91BPOIH3GKMAHKNNVV4KQNSO5AEMVJF66Q9ASUAAJG, AWS Error Code: UnrecognizedClientException, AWS Error Message: The security token included in the request is invalid. I'm not sure if fixing the problem should be a part of this issue, or should I create a new puzzle or issue for that. |
@carlosmiranda PR is merged, I've left todo in code saying we need to migrate old rexsl tests. Can we close this issue? |
@palyuga Sure, thanks! |
there is a puzzle in this code |
@palyuga Much obliged! I've added 30 mins to your account in payment "50003424". +30 added to your rating, current score is: +45 |
@carlosmiranda the last puzzle |
@carlosmiranda the puzzle #389 is still not solved. |
@carlosmiranda the only puzzle #354 is solved here. |
We're currently using the
rexsl-maven-plugin
package in order to perform integration testing ons3auth-rest
pages. However, it's been made obsolete after version 1.0 of ReXSL.Hence, it would be great if we can migrate to another form of automated testing, such as CasperJS. See http://www.yegor256.com/2014/06/21/casperjs-with-maven.html. I think it's better if we do it even before migrating to the latest ReXSL version (see #196).
200-e1abb509
/RendersHomePage.js:33-33: Migrate old tests from rexsl/scripts... #253 (by )The text was updated successfully, but these errors were encountered: