[webbeans-dev] Granularity of assertions in TCK

[Pete Muir]

Here is another guideline - use the <note> field in the audit - for  
example if you mark an assertion implicit or untestable, it's always  
worth adding a note. For example in the case of

-    <assertion id="a2">
+    <assertion id="a2" testable="false">
       <text>If the application invokes a contextual instance after it  
has been destroyed, the behavior is undefined.</text>

I would add a note like

<note>A statement about container specific behavior which is not spec  
defined</note>

the other common one is the spec making a note about how another spec  
behaves, for example

     <assertion id="a" testable="false">
       <text>As defined by the EJB specification, all stateful session  
beans are passivation capable. Stateless and singleton session beans  
are not passivation capable.</text>
     </assertion>

there should be a note like

       <note>Defined by EJB spec</note>

On 23 Jul 2009, at 03:57, Dan Allen wrote:

> Thanks for these guidelines Pete.