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

Ehnance and organize all testing tools & resources in one place #37

Closed
atsakiridis opened this issue Mar 4, 2016 · 0 comments
Closed

Comments

@atsakiridis
Copy link
Collaborator

Impacts, adding them as I go:

  • Move all needed node scripts in test/load-testing
  • Try to unify the 3 node scripts (i.e. server.js, server-secure.js and application-server.js) to one script that will serve the automated.html page both on http & https and also provide a REST service to retrieve the RCML for the circular tests
  • rename automated.html to webrtc-client.html and default to bob/1234 if no username/pass as passed in the URL
  • Get rid of the perl script for provisioning Restcomm Clients and spawning Chrome tabs (this will now happen through Sellenium) and use python for the same functionality now that it's still pretty minimal and porting will happen in a snap, so that we don't have so many code bases to maintain.
@atsakiridis atsakiridis self-assigned this Mar 4, 2016
@atsakiridis atsakiridis added this to the 1.0.0 GA release milestone Mar 4, 2016
@atsakiridis atsakiridis changed the title Ehnance and organize all testing resources in one place and Ehnance and organize all testing tools & resources in one place Mar 4, 2016
atsakiridis pushed a commit that referenced this issue Mar 4, 2016
…testing. Working on #37: Ehnance and organize all testing tools & resources in one place
@atsakiridis atsakiridis changed the title Ehnance and organize all testing tools & resources in one place Ehnance and organize all testing tools & resources in one place Mar 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant