# JS Testing

Just grabbing some miscellaneous facts about the js tests.

tag: :js or type: :js in system and request tests make capybara use chrome headless, and wait for js.

{% code title="<https://github.com/forem/forem/blob/master/spec/support/initializers/capybara.rb#L29-L44>" %}

```ruby


# adapted from <https://medium.com/doctolib-engineering/hunting-flaky-tests-2-waiting-for-ajax-bd76d79d9ee9>
def wait_for_javascript
  max_time = Capybara::Helpers.monotonic_time + Capybara.default_max_wait_time
  finished = false

  while Capybara::Helpers.monotonic_time < max_time
    finished = page.evaluate_script("typeof initializeBaseApp") != "undefined"

    break if finished

    sleep 0.1
  end

  raise "wait_for_javascript timeout" unless finished
end

```

{% endcode %}

interestingly, `initializeBaseApp` is the function that's awaited (or waited to be defined) - typeof is function - basically the file that's loaded defining this function (base.js.erb) *also* immediately calls the function - so the existence of the definition is evidence of its execution.

initializeBaseApp calls `initializePage` (or passes that to `InstantClick`, which I assume calls it on ready state?) - and we call initializeBaseApp at the end of that file:

```javascript

// FUNCTIONAL CODE FOR PAGE

  function initializeBaseApp() {
    InstantClick.on('change', function() {
      initializePage();
    });
    InstantClick.init();
  }
  
  
  
var instantClick
  , InstantClick = instantClick = function(document, location, $userAgent) {
//  ... SNIP ...
  
    function on(eventType, callback) {
      $eventsCallbacks[eventType].push(callback)
    }
}


// Start BaseApp for Page
  initializeBaseApp()
```

In my "I don't understand javascript" confusion - I wondered why "call function initializePage by name" was something that needed a closure - but I believe, if I understand it correctly, the closure exists to provide access to a named function that's not exported/public/global - or might not be?

I personally, maybe it's schemelang leaking through, would assume this were expressed better as a simply function arg:

```javascript
InstantClick.on('change', initializePage);
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://danuber.gitbook.io/public-notes/flaky-specs-1/js-testing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.