Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jasmine test suite possible? #2

Open
jywarren opened this issue May 26, 2016 · 8 comments
Open

Jasmine test suite possible? #2

jywarren opened this issue May 26, 2016 · 8 comments

Comments

@jywarren
Copy link
Collaborator

I'm using this with a pretty vanilla Woofmark instance but I get a few different behaviors when autocompleting. I'm trying to isolate them, but am wondering if a test suite would be possible. I'm no expert but could put together a simple Jasmine suite pretty easily if you're interested.

@bevacqua
Copy link
Owner

Please do!

@jywarren
Copy link
Collaborator Author

haha, ok, i will. But I'm going to need to read your book or something to
get my coding clean enough to be really helpful...

On Thu, May 26, 2016 at 3:13 PM, Nicolás Bevacqua [email protected]
wrote:

Please do!


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#2 (comment)

@bevacqua
Copy link
Owner

So glad you're working on all of these libs!

@jywarren
Copy link
Collaborator Author

Hi, I'm working on triggering the horsey appearance programmatically, and am trying to use the following to set off the horsey:

crossvent.fabricate(editor.editable,"keypress")

The .sey-item styles are being touched (I can see them flicker in the elements view of the dev console) but not shown, so I think I'm either not triggering the right event, or I haven't set the chunks correctly and perhaps it's not detecting that an insertion point or something? Any hints?

Thanks again for your help!

@bevacqua
Copy link
Owner

How are you updating chunks?

@jywarren
Copy link
Collaborator Author

I'm using the new editor.value() method, but could use something else if more appropriate. I haven't written tests for UI-event driven stuff like this before. Should I create a custom runCommand() and that'd trigger the horsey instance? It wasn't clear to me that that would work.

@jywarren
Copy link
Collaborator Author

Ah, that works!

@jywarren
Copy link
Collaborator Author

jywarren commented May 31, 2016

Had some slight problem which I filed as bevacqua/woofmark#29, but proceeding now, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants