Software Testing Strategy

[TravelsAsia]

Just checking you did not answer a Bitshares / Graphene question.

I actually did :P

@xeroc Is it the same test strategy for MUSE? 

Have no idea how it is done for MUSE. From what I remember, cob is building up an additional Graphene-C++-Lab for Peertracks ..

Gotcha! I was getting excited that there was something ready to test. :)

[xeroc]

Just checking you did not answer a Bitshares / Graphene question.

I actually did :P

@xeroc Is it the same test strategy for MUSE? 

Have no idea how it is done for MUSE. From what I remember, cob is building up an additional Graphene-C++-Lab for Peertracks ..

[betax]

@xeroc Is it the same test strategy for MUSE?  Just checking you did not answer a Bitshares / Graphene question.

[TravelsAsia]

Backend testing is currently done in-house by CNX (not meant for end users anyway)
Frontend testing can be done by anyone that knows how to use git and read the README file .. currently we have a 7-10 days release cycle

Thanks for the update. No idea on git, but I'll dig around on how to use it.

[xeroc]

Backend testing is currently done in-house by CNX (not meant for end users anyway)
Frontend testing can be done by anyone that knows how to use git and read the README file .. currently we have a 7-10 days release cycle

[TravelsAsia]

Could you tell us a little about the software testing strategy?  Since this product is targeted for general users, I hope this community has an opportunity to beat it up before it's officially released.