Activity
From 02/25/2025 to 03/26/2025
03/26/2025
- 05:46 PM Bug #9525: Testcases: incorrect placeholders in directory.xml.template and other configuration pr...
- Vladimir, these @build.xml@ files are written to handle conversion either via the fileset method (*-Z*) or the source...
- 03:30 PM Bug #9525: Testcases: incorrect placeholders in directory.xml.template and other configuration pr...
- Also, I would simplify things by removing all ‘old’ conversion targets entirely. I’d also rename the repository’s @zf...
- 03:25 PM Bug #9525: Testcases: incorrect placeholders in directory.xml.template and other configuration pr...
- Roger Borrello wrote:
> Vladimir Tsichevski wrote:
> > Review xfertestcases: r1687, r1696, r1711.
>
> You cut of... - 02:59 PM Bug #9525: Testcases: incorrect placeholders in directory.xml.template and other configuration pr...
- Vladimir Tsichevski wrote:
> Review xfertestcases: r1687, r1696, r1711.
You cut off the targets before the very i... - 02:15 PM Bug #9525: Testcases: incorrect placeholders in directory.xml.template and other configuration pr...
- Review xfertestcases: r1687, r1696, r1711.
Issues found in @build.xml@:
1. The @convert@ target does not depend... - 11:58 AM Bug #9525: Testcases: incorrect placeholders in directory.xml.template and other configuration pr...
- Vladimir Tsichevski wrote:
> I mean where can we find the changes? Which repositories, revisions?
The @xfer.golde... - 11:06 AM Bug #9525: Testcases: incorrect placeholders in directory.xml.template and other configuration pr...
- Roger Borrello wrote:
> Vladimir Tsichevski wrote:
> > Roger Borrello wrote:
> > > I believe this task is ready fo... - 09:08 AM Bug #9525: Testcases: incorrect placeholders in directory.xml.template and other configuration pr...
- Vladimir Tsichevski wrote:
> Roger Borrello wrote:
> > I believe this task is ready for review.
>
> Which change... - 07:53 AM Bug #9525: Testcases: incorrect placeholders in directory.xml.template and other configuration pr...
- Roger Borrello wrote:
> I believe this task is ready for review.
Which changes are we expected to review? - 09:26 AM Support #6859: preprocessor tests
- Greg Shah wrote:
> Tomasz can help with understanding the Harness approach including how to setup tests that can run... - 09:24 AM Support #6859: preprocessor tests
- Tomasz can help with understanding the Harness approach including how to setup tests that can run under both OE and F...
- 09:21 AM Support #6859: preprocessor tests
- > How should I test like in #6860?
> I created the tests in 4GL but when converting with FWD, FWD doesn't have @COMP... - 09:11 AM Support #6859: preprocessor tests
- Alexandru Lungu wrote:
> > There will be some tests which are hard to check in an ABLUnit test method. I still think... - 08:43 AM Support #6859: preprocessor tests
- Will look into harness for those tests that are using @compile@ statement.
- 07:37 AM Support #6859: preprocessor tests
- I will upload the test classes that I've done, if it's relevant for now.
- 07:31 AM Support #6859: preprocessor tests
- Greg,
I migrated all of the tests but with a few exceptions. I see that in @old_testcases@ there are these files:
*... - 04:40 AM Support #6859: preprocessor tests
- How should I test like in #6860?
I created the tests in 4GL but when converting with FWD, FWD doesn't have @COMPILER...
03/25/2025
- 08:49 AM Support #6859: preprocessor tests
- > There will be some tests which are hard to check in an ABLUnit test method. I still think we might need some level ...
- 08:45 AM Support #6859: preprocessor tests
- Nice. I think this approach can work well for some tests, maybe even all tests that are expected to "pass" in OE. F...
- 08:30 AM Support #6860: lexer tests
- In the OE testing, we only need to know if it compiled or not and if it failed to compile, the details (as you have a...
03/24/2025
- 10:27 AM Support #6859: preprocessor tests
- Created the following methods, adapted to the new @testcases@ project:...
- 08:08 AM Support #6859 (WIP): preprocessor tests
- Started looking through the existing tests in @old_testcases@ and executed them on Developer Studio
- 08:59 AM Support #6860: lexer tests
- Greg Shah wrote:
> To be clear: we will implement a driver that directly executes the lexer and checks the output. ...
03/21/2025
- 09:11 AM Support #6859: preprocessor tests
- In addition to #6859-3, we need to consider the following:
* The testing must be able to run in both OE and FWD.
...
03/20/2025
- 04:47 PM Support #6860: lexer tests
- We need to work on both the driver program as well as specific tests to check the full range of lexing behavior.
T...
03/19/2025
- 07:10 PM Bug #9525: Testcases: incorrect placeholders in directory.xml.template and other configuration pr...
- I believe this task is ready for review.
03/03/2025
- 09:30 AM Bug #9649 (Test): Plain JUnit5 tests cannot execute if p2j.jar is in classpath
- 09:22 AM Bug #9649: Plain JUnit5 tests cannot execute if p2j.jar is in classpath
- Greg Shah wrote:
> Merge to trunk after 9498a.
Merged as trunk rev. 15752. - 07:45 AM Bug #9649 (Merge Pending): Plain JUnit5 tests cannot execute if p2j.jar is in classpath
- Merge to trunk after 9498a.
03/01/2025
- 08:13 AM Bug #9649: Plain JUnit5 tests cannot execute if p2j.jar is in classpath
- I ran tests for our large customer’s application using trunk and 9649a, and the results were identical. I gather that...
02/28/2025
- 10:35 AM Bug #9649: Plain JUnit5 tests cannot execute if p2j.jar is in classpath
- Greg Shah wrote:
> I just don't want to commit to trunk and then find that we have caused a problem for existing ABL... - 08:34 AM Bug #9649: Plain JUnit5 tests cannot execute if p2j.jar is in classpath
- I just don't want to commit to trunk and then find that we have caused a problem for existing ABLUnit users (e.g. not...
- 08:04 AM Bug #9649: Plain JUnit5 tests cannot execute if p2j.jar is in classpath
- Greg Shah wrote:
> Have you tested ABLUnit tests in some non-trivial 4GL project?
Why?
This change addresses sit... - 07:57 AM Bug #9649: Plain JUnit5 tests cannot execute if p2j.jar is in classpath
- Have you tested ABLUnit tests in some non-trivial 4GL project?
- 03:54 AM Bug #9649: Plain JUnit5 tests cannot execute if p2j.jar is in classpath
- I've finished testing: with *trunk*, it is impossible to run JUnit5 tests in the @test/@ subdirectory.
With 9649a th...
02/27/2025
- 08:21 AM Support #6862: build conversion regression testing tooling
- Tomasz: Can you please summarize how the ChUI Regression testing handles this today? The older version of it had a s...
- 08:17 AM Support #6859: preprocessor tests
- We will implement a driver that directly executes the preprocessor and compares the resulting output against baseline...
- 08:15 AM Support #6860: lexer tests
- To be clear: we will implement a driver that directly executes the lexer and checks the output. We must check both v...
- 07:53 AM Support #6861: tests for valid and invalid 4GL syntax (parsing)
- After considering this further, I think we need 2 approaches:
1. For valid 4GL syntax, I think we make sure that w...
Also available in: Atom