On 28.05.2013 12:26, Lev A. Stejngardt wrote:
> Dear devs,
>
> I'd like to update the "Testing"[1] page on the Saros website. It
> seems like some points are out of date and some others don't belong
> there anymore. Here is a complete list of the content and my humble
> thoughts. If you don't mind I would like to edit this page.
>
> I would like to remove EVERY content from the page that isn't Saros specific.
>
> - How to run a manual test
>
> It seems to me that these are instructions for the testing manager.
> This is an internal matter, which should not be listed on this page.
This chapter is completely out of date (regarding the process)
> - How to debug
I think the whole debug content can be removed because:
1. you are debugging a multi-threaded application ...
2. just using log statement almost serves the same purpose
>
> Item 1 and 2 look like they are out of date. Can someone prove this?
> Item 3 explains how to set breakpoints -> that is cleary nothing
> "Saros specific" -> remove
> Item 4 tells you to switch to the debug view -> no Saros -> remove
> Item 5 explains shortcuts and what they do -> remove
> Item 6 explains the variables view -> remove
>
> Indeed these things are interesting but I don't think they belong
> there. Maybe we can keep these points and just move them to the "FAQ
> on daily pratice" ("daily practice") section?
>
> - How to run Saros STF tests locally?
>
> Should be renamed into "How to set up Saros for local STF tests" and
> moved to "daily practice". Or just retain there.
>
> - Starting Saros in test mode?
>
> Move to "daily practice" or retain there.
>
> - How to write Saros STF tests locally?
>
> I don't want to discuss this point now. It just needs another content
> because the provided content isn't very helpful.
>
> - How to run the JUnit test cases?
>
> Remove (because it's not Saros specific) or move it to "daily
> practice". I would like to move it to "daily practice". Interviewees
> had problems with running JUnit tests.
>
> - How to run test coverage analysis locally?
>
> Seems to be Saros specific. Can someone prove it? I'd like to keep it.
It is not Saros specific but keep in mind that it is possible for a code
review to run
the provided test cases with instrumented code to verify that you have
written
enough tests.
>
> - How to gain code coverage from STF run locally? (with EmmaEcl)
This can be removed as it is not needed ... the CI is already doing this
for free.
> Seems to be Saros specific. Can someone prove it? I'd like to keep it.
>
> BR, Leo
>
> [1] http://www.saros-project.org/testing
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> _______________________________________________
> DPP-Devel mailing list
> DPP-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dpp-devel
------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
DPP-Devel mailing list
DPP-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dpp-devel
