On 24 October 2011 12:59, Steven McCoy <[email protected]> wrote: > On 24 October 2011 09:37, Chuck Remes <[email protected]> wrote: > >> >> On Oct 22, 2011, at 4:55 PM, Steven McCoy wrote: >> >> > Another large integration project. Before I continue running through >> new tests it is probably a good idea for the code layout and infrastructure >> to be updated to all work cleanly. >> >> Fantastic! >> >> > I'm working through the tree and there are many concrete classes. There > might not be much testing possible. > > Run down on the modules, not the greatest of available coverage:
1: Good for testing: - array - atomic_counter - atomic_ptr - clock - mutex - options - pgm_socket - semaphore - signaler - tcp_socket - thread - trie - uuid 2: C code, not ideal: - blob - command - config - device - err - fd - ip - likely - msg_content - poller - windows - wire - zmq 3: Non-injectable dependencies or concrete classes. - connect_session - dist - fq - io_object - io_thread - lb - mailbox - named_session - object - pair - pgm_receiver - pgm_sender - pipe - poller_base - pub - pull - push - reaper - rep - req - session - socket_base - transient_session - xpub - xrep - xreq - xsub - zmq_connector - zmq_engine - zmq_init - zmq_listener 4: Abstract - ctx - decoder - encoder - own 5: Interfaces - i_engine - i_inout - i_poll_events 6: Could work with additional mocking. - swap (zmsg) - tcp_connecter (ip) - tcp_listener (ip) 7: Could work with template mocking. - ypipe - yqueue I guess I need to clone on github. -- Steve-o
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
