Update README.md
Showing
1 changed file
with
26 additions
and
0 deletions
README.md
0 → 100644
1 | # WebServicePlugins | ||
2 | Plugins for Visual Studio Loadtest and Webtest to handle SOAP and REST requests | ||
3 | and responses that use XML, JSON or MSBIN formats. Provides XPath based | ||
4 | verification and extraction rules, a request/response viewer in the webtest gui | ||
5 | results tab, and a request body editor for web tests. | ||
6 | |||
7 | ## Branches and versions of Visual Studio | ||
8 | The initial checkin to the master branch is a copy of the original code from | ||
9 | Codeplex of the VS2013 version of the plugin, taken 2017-09-02, version 3.2, | ||
10 | last built on December 28 2013. | ||
11 | |||
12 | This project has a master branch for the main logic, and separate branches for | ||
13 | specific code targeting specific versions of Visual Studio. I.e. code changes | ||
14 | specific for a VS version should be committed to the appropriate branch. Code | ||
15 | changes to common files should be committed to master, so the VS specific | ||
16 | version branches can merge with master to receive these updates, without having | ||
17 | to cherry pick commits. | ||
18 | |||
19 | This also means that the branches may NEVER be merged into master, since these | ||
20 | only contain VS version specific code changes. | ||
21 | |||
22 | Builds should only be created on the non master branches, for a specific version | ||
23 | of Visual Studio, although the master branch currently targets VS2013, there is | ||
24 | a specific branch for VS2013 as well. Changes that are needed to be committed | ||
25 | that are specific for VS2013 should therefor be committed to the vs2013 branch, | ||
26 | since these can not be allowed to be merged into the other version branches. | ||
... | \ No newline at end of file | ... | \ No newline at end of file |
-
Please register or sign in to post a comment