Smoke testing should include:

   1. Running all samples
   2. Running all automated tests
   3. Testing all new features for basic operation
   4. Testing overall product with management console for key functionality

Please do all of the above within the product team before submitting to QA
team

On Wed, Apr 27, 2011 at 4:06 AM, Denis Weerasiri <de...@wso2.com> wrote:

> Hi RMs,
> Carbon  packs are available at :
> http://10.100.1.43/~carbon/releases/carbon/3.2.0/latest/ .
> Please do a smoke test on your product and let QA team know whether the
> packs are ready for QA. Please prioritize this task.
>
> Some packs(brs,greg,esb etc) lacks the source packs.
>
> --
> Thanks,
> Denis
> ----------------------------------------------------------
> *Denis Weerasiri*
> Software Engineer; WSO2 Inc.; http://wso2.com,
> *email: denis <http://goog_277208233/>** [AT] wso2.com* <http://wso2.com/>
> *
> blog: **http://ddweerasiri.blogspot.com*<http://ddweerasiri.blogspot.com/>
> *
> twitter: **http://twitter.com/ddweerasiri*<http://twitter.com/ddweerasiri>
> *
> linked-in: 
> **http://lk.linkedin.com/in/ddweerasiri*<http://lk.linkedin.com/in/ddweerasiri>
>
>
> _______________________________________________
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
> Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
_______________________________________________
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to