Activity
From 01/22/2025 to 02/20/2025
02/14/2025
- 06:05 AM Feature #9650: Support for running on a server or in a docker container
- One of the features Harness supports is the ability to specify a time after which a test is considered to as failed f...
- 04:01 AM Feature #9650 (New): Support for running on a server or in a docker container
02/11/2025
- 12:15 PM Feature #9619: Forced test order
- > Isnt a goal running regression tests in automatic pipeline - possibly in many parallel sessions on the same server ...
- 12:08 PM Feature #9619: Forced test order
- I am suspending work on Fixed Test execution feature.
In order to fix issues specified in #9619-9 additional functio... - 07:35 AM Feature #9619: Forced test order
- Greg Shah wrote:
> > We'd need an in-depth test analysis which is time consuming and still gives uncertain results ?...
02/10/2025
- 07:34 AM Feature #9619: Forced test order
- Tomasz Domin wrote:
> Greg Shah wrote:
> > > I was rather thinking about "frame" for dependencies.
> >
> > Like ...
02/07/2025
- 02:14 PM Feature #9619: Forced test order
- Greg Shah wrote:
> > I was rather thinking about "frame" for dependencies.
>
> Like a phase of testing? We could... - 05:26 AM Feature #9619 (WIP): Forced test order
- Created task branch 9619a
02/06/2025
- 11:57 AM Feature #9619: Forced test order
- > I was rather thinking about "frame" for dependencies.
Like a phase of testing? We could add a dependency type f... - 11:36 AM Feature #9619: Forced test order
- Greg Shah wrote:
> Keeping dependency information in a separate file doesn't seem to be a good practice. Likewise, ... - 10:52 AM Feature #9619: Forced test order
- Keeping dependency information in a separate file doesn't seem to be a good practice. Likewise, adding a completely ...
- 04:49 AM Feature #9619: Forced test order
- Harness includes features that allows for controlling test execution order like (source : [[harness:Documentation]] a...
- 02:39 AM Feature #9619 (WIP): Forced test order
- 02:27 AM Feature #9284 (Review): Support for local terminal
- 02:27 AM Feature #9285 (Review): Allow remote access to Event Semaphores and Mutexes
02/04/2025
- 09:56 AM Feature #6265: generate junit-compatible xml results for output
- Tomasz Domin wrote:
> Created task branch @6265a@, implemented JUnit report exporting, Exported files are successful... - 09:10 AM Bug #9489 (Test): Support for different terminal encodings
- Task branch @9489b@ has been merged into @harness/trunk@ and archived.
02/03/2025
- 04:11 PM Bug #9489 (Merge Pending): Support for different terminal encodings
- You can merge it now.
- 04:00 PM Bug #9489: Support for different terminal encodings
- Tested branch @9489b@ with regression tests - both with and without #7657 branch @7657a@:
* for @7657a@ with followi... - 11:48 AM Feature #6265: generate junit-compatible xml results for output
- Created task branch @6265a@, implemented JUnit report exporting, Exported files are successfully imported into Eclips...
01/31/2025
- 08:58 AM Feature #6265 (WIP): generate junit-compatible xml results for output
- 08:31 AM Bug #9489 (Internal Test): Support for different terminal encodings
- Code Review Task Branch 9489a Revision 38
The changes are good. - 03:16 AM Bug #9489: Support for different terminal encodings
- Greg Shah wrote:
> Code Review Task Branch 9489b Revisions 36 and 37
>
> In @Terminal@, shouldn't we have some co...
01/30/2025
- 03:34 PM Bug #9489: Support for different terminal encodings
- Code Review Task Branch 9489b Revisions 36 and 37
In @Terminal@, shouldn't we have some code to handle cases where... - 02:32 PM Bug #9489: Support for different terminal encodings
- Tomasz Domin wrote:
> Eugenie - did you find the change working for you ? especially regarding #7657
Yes, your fi... - 02:24 PM Bug #9489: Support for different terminal encodings
- Eugenie - did you find the change working for you ? especially regarding #7657
Also available in: Atom