Mailspring/internal_packages/message-list/spec/message-toolbar-items-spec.cjsx

66 lines
2.4 KiB
Text
Raw Normal View History

React = require "react/addons"
ReactTestUtils = React.addons.TestUtils
TestUtils = React.addons.TestUtils
{Thread, FocusedContentStore, Actions, ChangeUnreadTask} = require "nylas-exports"
StarButton = require '../lib/thread-star-button'
ThreadToggleUnreadButton = require '../lib/thread-toggle-unread-button'
test_thread = (new Thread).fromJSON({
"id" : "thread_12345"
"account_id": TEST_ACCOUNT_ID
"subject" : "Subject 12345"
"starred": false
})
test_thread_starred = (new Thread).fromJSON({
"id" : "thread_starred_12345"
"account_id": TEST_ACCOUNT_ID
"subject" : "Subject 12345"
"starred": true
})
describe "MessageToolbarItem starring", ->
it "stars a thread if the star button is clicked and thread is unstarred", ->
spyOn(Actions, 'queueTask')
starButton = TestUtils.renderIntoDocument(<StarButton thread={test_thread}/>)
TestUtils.Simulate.click React.findDOMNode(starButton)
perf(*): Add indexes, optimize "shouldAcceptModel", optimize Tasks Summary: Consolidate the smarts from ChangeFolderTask into a generic ChangeMailTask ChangeMailTask: - only makes requests for threads / messages that actually changed - handles incrementing / decrementing locks - writes changes to the database in a single pass, and only writes modified models - encapsulates the undo state that was built into ChangeFolderTask This change means that ChangeLabelsTask enjoys the same "smarts" as ChangeFolderTask. Label changes resulting in no-ops do not create web requests, you can undo label changes and they go back to the correct previous state. Replace "UpdateThreadsTask" and "UpdateNylasObjectsTask" with subclasses based on the same code used for folder/labels This means that the naming and parameter sets are consistent for all thread/message changing tasks. It also means that starring/marking as use the same (tested) business logic and starring 999 already-starred threads doesn't create 999 requests. Go away DraftCountStore - nobody wants you in secondary windows Add "Debug query plans" option which prints out the steps the database is taking. Look for "SCAN" to now you're having a bad time. Make "version" field queryable, when we receive deltas/API response, find all versions of existing models in a single query without loading or parsing the objects Contact: Add index for lookup by email Label: add index for lookup by name Message: Add index for message body join table Test Plan: Run tests Reviewers: evan Reviewed By: evan Differential Revision: https://phab.nylas.com/D1840
2015-08-06 06:53:08 +08:00
expect(Actions.queueTask.mostRecentCall.args[0].threads).toEqual([test_thread])
expect(Actions.queueTask.mostRecentCall.args[0].starred).toEqual(true)
it "unstars a thread if the star button is clicked and thread is starred", ->
spyOn(Actions, 'queueTask')
starButton = TestUtils.renderIntoDocument(<StarButton thread={test_thread_starred}/>)
TestUtils.Simulate.click React.findDOMNode(starButton)
perf(*): Add indexes, optimize "shouldAcceptModel", optimize Tasks Summary: Consolidate the smarts from ChangeFolderTask into a generic ChangeMailTask ChangeMailTask: - only makes requests for threads / messages that actually changed - handles incrementing / decrementing locks - writes changes to the database in a single pass, and only writes modified models - encapsulates the undo state that was built into ChangeFolderTask This change means that ChangeLabelsTask enjoys the same "smarts" as ChangeFolderTask. Label changes resulting in no-ops do not create web requests, you can undo label changes and they go back to the correct previous state. Replace "UpdateThreadsTask" and "UpdateNylasObjectsTask" with subclasses based on the same code used for folder/labels This means that the naming and parameter sets are consistent for all thread/message changing tasks. It also means that starring/marking as use the same (tested) business logic and starring 999 already-starred threads doesn't create 999 requests. Go away DraftCountStore - nobody wants you in secondary windows Add "Debug query plans" option which prints out the steps the database is taking. Look for "SCAN" to now you're having a bad time. Make "version" field queryable, when we receive deltas/API response, find all versions of existing models in a single query without loading or parsing the objects Contact: Add index for lookup by email Label: add index for lookup by name Message: Add index for message body join table Test Plan: Run tests Reviewers: evan Reviewed By: evan Differential Revision: https://phab.nylas.com/D1840
2015-08-06 06:53:08 +08:00
expect(Actions.queueTask.mostRecentCall.args[0].threads).toEqual([test_thread_starred])
expect(Actions.queueTask.mostRecentCall.args[0].starred).toEqual(false)
describe "MessageToolbarItem marking as unread", ->
thread = null
markUnreadBtn = null
beforeEach ->
thread = new Thread(id: "thread-id-lol-123", accountId: TEST_ACCOUNT_ID)
markUnreadBtn = ReactTestUtils.renderIntoDocument(
<ThreadToggleUnreadButton thread={thread} />
)
it "queues a task to change unread status to true", ->
spyOn Actions, "queueTask"
ReactTestUtils.Simulate.click React.findDOMNode(markUnreadBtn).childNodes[0]
changeUnreadTask = Actions.queueTask.calls[0].args[0]
expect(changeUnreadTask instanceof ChangeUnreadTask).toBe true
expect(changeUnreadTask.unread).toBe true
expect(changeUnreadTask.threads[0].id).toBe thread.id
it "returns to the thread list", ->
spyOn Actions, "popSheet"
ReactTestUtils.Simulate.click React.findDOMNode(markUnreadBtn).childNodes[0]
expect(Actions.popSheet).toHaveBeenCalled()