TASK: Create tests about svn-scm HOT 33 CLOSED

Yes, testing would help a lot.

from svn-scm.

Tests will also make CI possible

from svn-scm.

@edgardmessias Travis CI is setup and the first build passed.

from svn-scm.

Nice!

from svn-scm.

Iv added a prettier style guide check to Travis CI

from svn-scm.

Maybe, we can use a https://coveralls.io/, https://codeclimate.com/, https://scrutinizer-ci.com/, ....

codeclimate has support to typescript

from svn-scm.

codacy?

from svn-scm.

Also good

from svn-scm.

https://codecov.io/ - Example: https://github.com/codecov/example-typescript-vscode-extension

from svn-scm.

Added the codecov stuff not sure how it works

from svn-scm.

Let's use CodeClimate for now

Can you reverse those changes?

from svn-scm.

reverted

from svn-scm.

Added a tslint file for code style. This may need tweaking.

from svn-scm.

See the project: https://github.com/vscode-icons/vscode-icons, We can use it as a base

from svn-scm.

copied that. You can tweak as needed. I'm not fussed by style guides as long as we all stick to one.

from svn-scm.

We can use the codecov and bithound from vscode-icons

from svn-scm.

Okay ill have a look tomorrow

from svn-scm.

could not get codcov to work. Their support was also poor.

from svn-scm.

CodeCov Working

from svn-scm.

Thanks for that. You adding appvoyer or should i?

from svn-scm.

You can add AppVoyer

from svn-scm.

AppVoyer added and working

from svn-scm.

@JohnstonCode, We now need to break the code into smaller parts so we can test

from svn-scm.

@edgardmessias what would you suggest we break apart?

I'm still not 100% on how we can test the extension fully. We might need to make some scripts that create a test Svn repository. I know the Mg SCM uses Powershell scripts to test.

from svn-scm.

XML Parser, command builder for cp.spawn, status parser.

Then we can start building local repositories for real test.

from svn-scm.

Yes nice and simple.

We will need to script the creation of local repositories so they can run on Travis and AppVoyer.

I can write a PowerShell and bash script for that.

from svn-scm.

First: create an XML parser
Second: Status Parser
Third: Command builder for cp.spawn

from svn-scm.

The command builder is just this function

Status parser is this function

XML stuff does need grouping (might be something on npm)

from svn-scm.

Add in Status parser:

from svn-scm.

Think that should be left separate from the parser as they have two very distinct jobs. StatusAssigner maybe?

from svn-scm.

Good

from svn-scm.

Also, i think anything we are working on making an issue so no work is duplicated

from svn-scm.

To add new tests, open new issue.

from svn-scm.