Make update test a little stronger

`update` should retain old values. This could be made even better with some level of validation (middleware?).

Author: bebraw

immutable_app/tests/lane_reducer_test.js

@@ -45,6 +45,7 @@ describe('LaneReducer', () => {
  assert.equal(lanes.count(), 1);
  assert.equal(lanes.get(0).get('id'), lane.id);
  assert.equal(lanes.get(0).get('name'), updatedName);
+ assert.equal(lanes.get(0).get('notes').count(), 0);
  });
 
  it('should not crash while updating a non-existent lane', () => {

immutable_app/tests/note_reducer_test.js

@@ -22,7 +22,8 @@ describe('NoteReducer', () => {
  it('should update notes', () => {
  const note = {
  id: 'foobar',
- task: 'test'
+ task: 'test',
+ editing: true
  };
  const updatedTask = 'foofoo';
 
@@ -39,6 +40,7 @@ describe('NoteReducer', () => {
  assert.equal(state.count(), 1);
  assert.equal(state.get(0).get('id'), note.id);
  assert.equal(state.get(0).get('task'), updatedTask);
+ assert.equal(state.get(0).get('editing'), note.editing);
  });
 
  it('should not crash while updating a non-existent note', () => {