Skip to content

Test case for editor and mode #114

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

Open
gaocegege opened this issue Jun 12, 2017 · 0 comments
Open

Test case for editor and mode #114

gaocegege opened this issue Jun 12, 2017 · 0 comments

Comments

@gaocegege
Copy link
Member

gaocegege commented Jun 12, 2017

ref #10 (comment)

  • Testing the editor: is there any specific editor testing that needs to be done, or should that be left to Processing?

I am not sure which layer we should put the test in. But if Processing does it, it works for Processing.R, too. And I will file a new issue about it and try to do a research.

  • Testing the mode itself: perhaps open a separate issue (unscheduled, no milestone) for this to come back to it in the future.

Yeah, it is helpful. I am not sure if the mode test and the editor test are the same thing, we could put them in one issue.

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

No branches or pull requests

1 participant