- **status**: unassigned --> accepted
- **assigned_to**: Canh Truong


---

** [tickets:#1913] log: improve test cases for log service**

**Status:** accepted
**Milestone:** 5.1.FC
**Created:** Thu Jul 14, 2016 03:30 AM UTC by Vu Minh Nguyen
**Last Updated:** Thu Jul 14, 2016 03:30 AM UTC
**Owner:** Canh Truong


Most test cases for the log service are made in a simplified way compared to 
how the log service should be handled when used by an application. Because of 
such simplifications test cases may report FAIL or even abort also if the log 
service not actually has failed. To get rid of this problem there are two 
things that should be improved:

1) Many (all) of the APIs may return SA_AIS_ERR_TRY_AGAIN this is not a fault 
and should normally not fail a test case instead proper TRY AGAIN handling 
should be used with all API function calls. 
2) Several test cases have dependency on other test cases. Will make them 
independence on others. 
3) Many test cases do change settings such as IMM attribute values before 
running tests, but not restore them back to previous values. 


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to