Re: [Dev] Test plan for DevStudio

2013-11-19 Thread Selvaratnam Uthaiyashankar
On Tue, Nov 19, 2013 at 11:36 AM, Susinda Perera susi...@wso2.com wrote:


 Hi DevStudio Team mates

 As we all know that we encountered number of  bugs in devs in recent past(and 
 some bad comments). I hope we could surely reduce many
 number of these bugs/complains if we have a proper test plan, but testing
 of 20+ different projects we support in DEVS and 40+ mediators within the
 ESB editor is not an easy task (we may need some automated testing etc.).
 But for testing of basic features like installing, running, import, saving,
 deploying features in DevStudio we need to formulate a proper test plan. As
 an initiative i propose following matrix, please share your ideas on
 this.




 win32 win64 linux32 linux64 mac32 mac64







  1 Running of DEVS Installed eclipse distributions ✓✓
  ✓
 ✓✓ ✓
  2 Installing zipped distributions on fresh eclipse (juno for nuw) ✓
 ✓
  ✓
 ✓✓ ✓
  3 Step 1 for a installed devs from zip file ✓
 ✓
 ✓
 ✓ ✓✓
   4 Import features





  4.1 Importing a esb project


 ✓


  4.2 Importing a single artifact


 ✓

  4.3 Importing a synapse.xml and generate artifacts


 ✓


  4.4 Use of old workspace in a newly released devstudio


 ✓










  5 ESB graphical editor





  5.1 Navigate back and forth in design and source view


 ✓


  5.2 Copy paste in source and navigate to design view


 ✓










  6 Saving





  6.1 Saving projects, artitacts


 ✓


  6.2 Saving and reopening (to test whether we miss any)


 ✓










  7 Deploying





  7.1 Deploying a simple car project from eclipse


 ✓


  7.2 Car file generation and deploying from carbon server mgt console


 ✓




 To have an extended test (covering all projects/mediators) it would be
 great if we can get the QA team support (at least before a major release),
 And i believe this testing would be easy if some of our team members
 could carry out their development on windows machines, where we could
 identify the issues while we develop.
 @Harshana : How about requesting couple of windows copies for our team?
 And requesting for QA?



Folks,

DevStudio is suppose to be used by Developers. Why do you need QA to test
that? Please note the mail I sent about product teams testing their
products.






 --
 *Susinda Perera*
 Software Engineer
 Mobile:(+94)716049075

 WSO2 Inc. http://wso2.com/
 Tel : 94 11 214 5345 Fax :94 11 2145300


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
S.Uthaiyashankar
VP Engineering
WSO2 Inc.
http://wso2.com/ - lean . enterprise . middleware

Phone: +94 714897591
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Test plan for DevStudio

2013-11-18 Thread Susinda Perera
Hi DevStudio Team mates

As we all know that we encountered number of  bugs in devs in recent past
(and some bad comments). I hope we could surely reduce many number of these
bugs/complains if we have a proper test plan, but testing of 20+ different
projects we support in DEVS and 40+ mediators within the ESB editor is not
an easy task (we may need some automated testing etc.). But for testing of
basic features like installing, running, import, saving, deploying features
in DevStudio we need to formulate a proper test plan. As an initiative i
propose following matrix, please share your ideas on this.




win32 win64 linux32 linux64 mac32 mac64







 1 Running of DEVS Installed eclipse distributions ✓✓
✓
✓✓✓
 2 Installing zipped distributions on fresh eclipse (juno for nuw) ✓
✓
✓
✓✓✓
 3 Step 1 for a installed devs from zip file ✓
✓
✓
✓✓✓
 4 Import features





 4.1 Importing a esb project


✓


 4.2 Importing a single artifact


✓

 4.3 Importing a synapse.xml and generate artifacts


✓


 4.4 Use of old workspace in a newly released devstudio


✓










 5 ESB graphical editor





 5.1 Navigate back and forth in design and source view


✓


 5.2 Copy paste in source and navigate to design view


✓










 6 Saving





 6.1 Saving projects, artitacts


✓


 6.2 Saving and reopening (to test whether we miss any)


✓










 7 Deploying





 7.1 Deploying a simple car project from eclipse


✓


 7.2 Car file generation and deploying from carbon server mgt console


✓




To have an extended test (covering all projects/mediators) it would be
great if we can get the QA team support (at least before a major release),
And i believe this testing would be easy if some of our team members could
carry out their development on windows machines, where we could identify
the issues while we develop.
@Harshana : How about requesting couple of windows copies for our team? And
requesting for QA?



-- 
*Susinda Perera*
Software Engineer
Mobile:(+94)716049075

WSO2 Inc. http://wso2.com/
Tel : 94 11 214 5345 Fax :94 11 2145300
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev