Better ways to test Universal apps about universal HOT 5 CLOSED

Consider a decoupling the view using other methods such as the one described in this post
https://medium.com/how-we-build-fedora/protractorjs-a-better-way-to-implement-page-objects-bc927cdb3f69

from universal.

similar to #44 where there is a test environment with helper syntax in html or js that should be removed in other envs

from universal.

This is for a future refactor:

Thinking about it more each test should be isolated for each it block. So each it block is testing a certain feature which means you can include a test for each state of the app.

something like

state('should have checked values for checkbox inputs', {
  // should run anywhere
  universal: function() {
    // noop
    expect(subject).toEqual(result);
  },
  server: function() {
    // check attr
    expect(subject).toEqual(result);
  },
  client: function() {
    // check prop
    expect(subject).toEqual(result);
  },
  preboot: function() {
    // checked should transfer from attr to prop
    expect(subject).toEqual(result);
  }
}

Where you can noop or just not include a function for the env you're not testing for. Otherwise the code you're writing, for example, to check the checked value of an input is either in separate files or 3 different scroll positions in your large test file

from universal.

we can just close this for now since it's experimental

from universal.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}

from universal.