test(weex): support to test the virtual dom generated form *.vue file #6944
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Compile the *.vue file into js code, then run it in Weex context, and compare the generate virtual dom. It’s a black-box testing for `weex-template-compiler`, `weex-styler`,`weex-vue-framework` and `weex-js-runtime`.
erweixin
pushed a commit
to erweixin/vue
that referenced
this pull request
Dec 15, 2017
vuejs#6944) Compile the *.vue file into js code, then run it in Weex context, and compare the generate virtual dom. It’s a black-box testing for `weex-template-compiler`, `weex-styler`,`weex-vue-framework` and `weex-js-runtime`.
lovelope
pushed a commit
to lovelope/vue
that referenced
this pull request
Feb 1, 2018
vuejs#6944) Compile the *.vue file into js code, then run it in Weex context, and compare the generate virtual dom. It’s a black-box testing for `weex-template-compiler`, `weex-styler`,`weex-vue-framework` and `weex-js-runtime`.
This was referenced Mar 14, 2018
f2009
pushed a commit
to f2009/vue
that referenced
this pull request
Jan 25, 2019
vuejs#6944) Compile the *.vue file into js code, then run it in Weex context, and compare the generate virtual dom. It’s a black-box testing for `weex-template-compiler`, `weex-styler`,`weex-vue-framework` and `weex-js-runtime`.
aJean
pushed a commit
to aJean/vue
that referenced
this pull request
Aug 19, 2020
vuejs#6944) Compile the *.vue file into js code, then run it in Weex context, and compare the generate virtual dom. It’s a black-box testing for `weex-template-compiler`, `weex-styler`,`weex-vue-framework` and `weex-js-runtime`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
devbranch for v2.x (or to a previous version branch), not themasterbranchOther information:
Compile the
*.vuefile into js code, then run it in Weex context and compare the render result with the expected virtual dom tree.It’s black-box testing for
weex-template-compiler,weex-vue-framework,weex-stylerandweex-js-runtime. The source code of the first two packages is in the current repo.The test files are put in the
test/weex/cases:render/: One-off render test cases.[name].vue: Source code.[name].vdom.js: Expected virtual dom tree.event/: Test cases which contain event bindings.[name].vue: Source code.[name].before.vdom.js: The first rendered virtual dom.[name].after.vdom.js: The updated virtual dom after the event dispatch.