Skip to content
This repository was archived by the owner on Aug 4, 2018. It is now read-only.

some questions #19

Open
GuyMograbi opened this issue Aug 10, 2016 · 3 comments
Open

some questions #19

GuyMograbi opened this issue Aug 10, 2016 · 3 comments

Comments

@GuyMograbi
Copy link

I really want to start using this project and see what it can do, since it looks so awesome and all, but I get the feeling it's too early, right?

When will you have an official release?

I am currently missing:

  • reports
  • documentation on actions

if I had those two, I feel like I could start using the project.

@GuyMograbi
Copy link
Author

GuyMograbi commented Aug 10, 2016

Another question

I wrote a test on a page that loads a really big resource - it takes a couple of seconds to load it - and yet the test says time < 50ms..

{
    "variables":[],
    "steps": [
        {
            "action": "open_url",
            "value": "http://localhost:3000/"
        }
    ]
}

this is our scenario, and this is the page's network

image

this is the test results

[
  {
    "url": "http://localhost:3000/",
    "success": true,
    "start": 1470832871748,
    "end": 1470832871793,
    "time": 45,
    "step": "{\"action\":\"open_url\",\"value\":\"http://localhost:3000/\"}"
  }
]
[
  {
    "url": "http://localhost:3000/",
    "success": true,
    "start": 1470832871748,
    "end": 1470832871793,
    "time": 45,
    "step": "{\"action\":\"open_url\",\"value\":\"http://localhost:3000/\"}"
  }
]

@james-braund-gw
Copy link

Hi Guy,

Can't speak for the original creators of this repo, but in our Development team we started using Felt a couple of months ago for a new project as a potential alternative to paid-for tools, used in conjunction with AWS EC2 instances to act as executors. We've made a few extensions to the original repo in our private fork, which I'm planning on offering to this repo at some point - hopefully you'll find them useful.

In terms of documentation for the actions - as you've seen, there isn't any to speak of! We found that using worker.js (https://github.com/kidk/felt/blob/master/worker.js) as a point of reference let us figure out the available actions, and extend them - form around line 150 onwards.

When we ran our performance tests, we primarily used server-side monitoring to check on the performance, but monitoring the results the client sees would be useful. There's some interesting info on the PhantomJS site about network monitoring, which might be a good starting point:

http://phantomjs.org/network-monitoring.html

I realise none of this solves your problems, but hopefully it gives you an idea of what others have done with it. Best of luck!

Cheers,
James

@kidk
Copy link
Owner

kidk commented Aug 12, 2016

Hi @GuyMograbi, thanks for your questions. It's great to see people interested in Felt.

It is still very much a work in progress, but certainly not dead 😄 I agree with your feedback in regards to the docs and will try to expand on them when I have the chance.

The long request you're not seeing is probably a bug. I will research and notify here when I've found the issue.

In terms of an official release I first want to have some quality control in place. (Tests, code style, ...) Soon after I release the first 'beta' version.

@james-braund-gw Thanks for sharing your experience and feedback, it always nice to hear that other people are using Felt. Very interested to see which changes you've made!

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

No branches or pull requests

3 participants