Build Testing

[tylerkrupicka]

One of the hardest parts of this project is testing because so much of the builds require external packages that run against the file system. Mocking lots of files would be an improvement, but also difficult.

I'd love to see some out-of-the-box thinking with regard to testing this project. Can we test scaffolding a new repo? Can we test a component build with different settings?

I'm open to suggestions and contributions in this space, but it may require looking at other projects like Create React App to see what they do.

[chopkarankit]

testing the application is a very easy part only you know what type of testing you do and on which module you test and which module is not test .

[tirthjivani]

@chopkarankit and @tylerkrupicka the part you both are talking about 'Testing' depends on how robust the code is and how much segregated the code files are. I would be glad to tell you that I have worked on two different projects one with documented testing and one project with no direction. It took no time in the first project but the second project shooked every breath of ours for testing.

There are many techniques for testing a project, try this Software Testing Help. And it's very important to maintain track of where exactly the process is going and what were the needs.

Looking forward to contributing.

[anjaliguptaz]

@tylerkrupicka I see codecov integration not there for this project https://codecov.io/gh/intuit/design-systems-cli