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

Comments for Testing in the Web Environment #101

Open
phinjensen opened this issue Nov 11, 2017 · 3 comments
Open

Comments for Testing in the Web Environment #101

phinjensen opened this issue Nov 11, 2017 · 3 comments

Comments

@phinjensen
Copy link
Contributor

phinjensen commented Nov 11, 2017

Comments for https://www.endpointdev.com/blog/2009/02/testing-in-web-environment/
By Jeff Boes

To enter a comment:

  1. Log in to GitHub
  2. Leave a comment on this issue.
@phinjensen
Copy link
Contributor Author

original author: Ethan Rowe
date: 2009-02-13T19:59:00-05:00

For JavaScript-focused testing, I've used a Javascript testing module similar in design to Perl's Test::More, provided by the OpenJSAN project. The project home page seems rather stale, but the testing module works for simple stuff. For Ajax-oriented tested, it's tricky to manage the concurrency issues.

http://openjsan.org/doc/t/th/theory/Test/Simple/0.21/index.html

  • Ethan

@phinjensen
Copy link
Contributor Author

original author: Nath
date: 2009-02-13T23:32:00-05:00

Very informative article. Much of what is discussed is framework/tool support for Test Execution automation. By far test design (like reducing the test combinations for example) and test data creation, the tool support is less. We are working on a free online tool called http://www.TestersDesk.com that addresses these needs. TestersDesk has a big roadmap and a lot of new tools are under development. Also, next week we are releasing a interface rich build (which will also be the first official release moving out of beta).

@phinjensen
Copy link
Contributor Author

original author: Kevin
date: 2010-01-03T17:14:43-05:00

"The drawback of Selenium is that since it must be run in an environment that includes a browser and window display system, you'll almost certainly need to run your test script on a workstation, or a server with all the windowing software installed."

I don't consider this a drawback. I want Firefox to participate in my tests. I want to be able to switch between displayed Selenium RC and "headless Selenium RC" (w/ Xvfb). At times I like to record using xv and xwd, and playback using convert and jpegs. But I'll confess that I've only just begun to get the playback part to hang together in my sandbox. I would have been further along w/ Perl, but, I chose to use Haskell along with Selenium RC.

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