feat: add performCount to derived state

[paoloricciuti]

Closes #87

This also kinda setup the testing for the derived state (which i think we should test separately for each field and following this pattern of adding the expected values in the each)...let me know what you think about it.

[beerinho]

Is exporting the tasks from the tests/components/... folder setting it up for something else? If not we probably don't need the exports.

Out of curiosity, do you usually prefer to use an object perform_count : {expected} over a string/number expected_perform_count?

[paoloricciuti]

Is exporting the tasks from the tests/components/... folder setting it up for something else? If not we probably don't need the exports.

Those exports are imported in the test after the render so that we can check what's inside the store.

Out of curiosity, do you usually prefer to use an object perform_count : {expected} over a string/number expected_perform_count?

I just did that because for other derived state we might need more values so it's not everything inside the single object but we can organize the values in terms of the derived state they refer to. But we can change that.

[beerinho]

Is exporting the tasks from the tests/components/... folder setting it up for something else? If not we probably don't need the exports.

Those exports are imported in the test after the render so that we can check what's inside the store.

Ah yeah, so they are

I just did that because for other derived state we might need more values so it's not everything inside the single object but we can organize the values in terms of the derived state they refer to. But we can change that.

I see, I guess a single object with all derived state might make more sense:

expected_state: {
  perform_count: 5	  
}

But we can change that if needed later on