Use descriptive test names instead of generic test_n

[StrongestNumber9]

Description

A test fails. It is called syslogStream_test_1. What does it do compared to syslogStream_test_2?

Use case or motivation behind the feature request

All tests should have descriptive names so you can know what it is testing just by looking at the name alone.
syslogStream_test_1 and syslogStream_test_2 should be called more like testSyslogStreamSending and testSyslogStreamSendingFailure

Related issues

pth_10/src/test/java/com/teragrep/pth10/SyslogStreamTest.java

Lines 165 to 167 in 57586b4

	@Test
	@EnabledIfSystemProperty(named="runSparkTest", matches="true") // teragrep exec syslog stream
	public void syslogStream_test_1() throws StreamingQueryException, InterruptedException, IOException {

pth_10/src/test/java/com/teragrep/pth10/SyslogStreamTest.java

Lines 207 to 209 in 57586b4

	@Test
	@EnabledIfSystemProperty(named="runSparkTest", matches="true") // teragrep exec syslog stream, with preceding aggregation command
	public void syslogStream_test_2() throws StreamingQueryException, InterruptedException, IOException {

Additional context

Haven't gone through most of the tests, this is just something I noticed when test got stuck and I went to check what it was supposed to be doing.

[Abigael-JT]

Pull requests:

• issue-226 Renamed unit tests  #391
• Renamed unit tests #408