[
https://issues.apache.org/jira/browse/AMQ-8322?focusedWorklogId=767144&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767144
]
ASF GitHub Bot logged work on AMQ-8322:
---------------------------------------
Author: ASF GitHub Bot
Created on: 06/May/22 11:16
Start Date: 06/May/22 11:16
Worklog Time Spent: 10m
Work Description: gemmellr commented on PR #729:
URL: https://github.com/apache/activemq/pull/729#issuecomment-1119508345
>
> @gemmellr thank you for your prompt review. Please characterize in more
detail (or point to an example) of a _unit_ test as you described.
>
A unit test tests a particular unit, not the entire thing. The API changes
that affect the Message instances for example, almost none of them actually
need a message to be sent or received, they are largely orthoganl. Even the
ones that you might want to system test 'for completeness', the underlying
behaviour can still be unit tested more closely without a broker. The new
producer API as another example, a significant chunk of that can be tested
without ever creating a connection.
There are many different approaches, but a basic thing as I just covered
would be I wouldnt expect the whole client or a broker to be needed at all for
many of the checks for the stuff being added, which is largely just a new API
for using existing functionality. The new bits can be tested in isolation. A
lot of the stuff being tested never needs to hit the wire and so never needs a
broker or the time wasted on starting it and connecting to it etc, or waiting
on messages to be consumed to check things easily verified before they were
ever actually sent etc.
> I'm happy to re-work and improve test execution time and structure. Others
had requested test coverage for message types and ack modes.
There are other ways to cover things. E.g unit tests. Running the same
system test over and over and varying things that ultimately have almost no
relation to the thing being tested, is a complete waste of time.
Issue Time Tracking
-------------------
Worklog Id: (was: 767144)
Time Spent: 14h (was: 13h 50m)
> Implement JMS 2.0 Connection createContext methods
> --------------------------------------------------
>
> Key: AMQ-8322
> URL: https://issues.apache.org/jira/browse/AMQ-8322
> Project: ActiveMQ
> Issue Type: New Feature
> Reporter: Matt Pavlovich
> Assignee: Matt Pavlovich
> Priority: Major
> Labels: #jms2
> Fix For: 5.18.0
>
> Time Spent: 14h
> Remaining Estimate: 0h
>
> Add support for JMSContext, JMSProducer and JMSConsumer for working with
> queues
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
