Fest Assertions 2.0M8 release

[Joel Costigliola]

Hi all,

Fest Assertions 2.0M8 has been released, it is available in maven central.

Maven dependency snippet :
<dependency>
   <groupId>org.easytesting</groupId>
   <artifactId>fest-assert-core</artifactId>
   <version>2.0M8</version>
</dependency>

Documentation is here : https://github.com/alexruiz/fest-assert-2.x/wiki

New and noteworthy in 2.0M8

Breaking changes :

• Remove dependency on AWT : AWT assertions moved to a new module
• Use java 6 instead of java 5

New features :

• github#79 : String assertions are available on (small) file by calling contentOf(File) method (Olivier Michallat)
• github#73 : new assertion ListAssert.has(Condition, Index) (Bo Gotthardt)
• github#97 : new assertion ListAssert.is(Condition, Index) (Bo Gotthardt)
• github#50 : new assertion StringAssert.containsOnlyOnce (Pauline Iogna)

Improvement :

• github#87 : Fail.failBecauseExpectedExceptionWasNotThrown now takes a Throwable instead of an Exception
• github#86 : tests : org.fest.assertions.internal contain too much classes
• github#82 : tests : org.fest.assertions.api contain too much classes (Olivier Michallat)
• github#91 : tests : move fail tests in a "fail" subpackage
• github#106 : provide better extensibility by exposing assertion WritableAssertionInfo
• github#74 : ObjectAssert lenient equals assertions now takes inherited fields into account

Bug :

• github#92 : Fix BinaryDiff_diff_File_byteArray_Test test that was failing on windows
• github#104 : containsExactly does not work with SortedSet

Refactoring

• Move creation of ArrayLists into a Lists class
• Move creation of Sets to Sets class
• Move Iterable-related methods out of the Collections
• Iterables : Rename 'isEmpty' to 'isNullOrEmpty'
• Move back factory of primitive arrays from fest-util back to fest-assert

Thanks to Pauline Iogna, Bo Gotthardt and Olivier Michallat for their contributions !

Have good assertions guys !
Cheers,

Joel

[Mark Derricutt]

Hi…

I see this breaks compatibility in fest-util with fest-reflect:

java.lang.NoSuchMethodError: org.fest.util.Strings.isEmpty(Ljava/lang/String;)Z

at org.fest.reflect.field.FieldName.validateIsNotNullOrEmpty(FieldName.java:73)

at org.fest.reflect.field.FieldName.beginFieldAccess(FieldName.java:66)

at org.fest.reflect.core.Reflection.field(Reflection.java:203)

at smx3.validation.ValidationAdviceTest.init(ValidationAdviceTest.java:35)

In my project, I've nominally been excluding the fest-util dep for fest-reflect and using the version depended on by fest-assert, which worked fine for M7, but M8 seems to bring in a new fest-util version which now breaks…

--
You received this message because you are subscribed to the Google Groups "easytesting" group.
To view this discussion on the web visit https://groups.google.com/d/msg/easytesting/-/Oqprc_cUBHcJ.
To post to this group, send email to easyt...@googlegroups.com.
To unsubscribe from this group, send email to easytesting...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/easytesting?hl=en.

[Alex Ruiz]

My bad, I'm sorry Mark. I made some changes to FEST-Util (for the better, of course)...but I didn't test it properly.

Thanks for reporting this.

Cheers,

-Alex

[Alex Ruiz]

I'm fixing fest-reflect as we speak. Once again, thanks Mark for reporting this issue :)

Cheers,

-Alex

[Johannes Schneider]

Any news to this topic? I run into the same problem...

[Alex Ruiz]

Sorry, Johannes, I haven't finished yet. I started to work on it, but
got busy at work.

I hope this week I'll have more time.

-Alex

> https://groups.google.com/d/msg/easytesting/-/A0HD7UNKxfUJ.

[Johannes Schneider]

I have this kind of NoSuchMethodError since a long time.

So maybe it is a good idea to readd that method to org.fest.util.Strings?

Could be marked as deprecated...

[Johannes Schneider]

I readded that method:

  @Deprecated

  public static boolean isEmpty(String s) {

    return isNullOrEmpty( s );

  }

Works well now. Would love to see that fixed like that. This gives the flexibility to combine different versions of fest-assert and fest-reflect

[Johannes Schneider]

Okay, I don't wanna be impatient here. But this is a real pain for me. I have to work around this issue since quite a long time. Today I tried to make some releases and run into the problems again.

I think the fix should be very easy and could be applied in a few minutes. If  you can't find the time, I'd be glad to make the commit.

On Saturday, 27 October 2012 18:01:14 UTC+2, Alex Ruiz wrote:

[Alex Ruiz]

Hey Johannes!

Thanks so much for the pull request! I was already working on fixing it, but found stuff in fest-reflect that needed fixes as well, in particular:

1. Removing decorators.
2. Updating tests to use the JUnit rules

#1 is taking me a little longer than expected though. I hope to have it fixed by beginning of next year.

Cheers,
-Alex

To view this discussion on the web visit https://groups.google.com/d/msg/easytesting/-/xZu95Tp7hoQJ.

[Alex Ruiz]

I'm currently in the process of releasing of compatible versions of all the modules.

I expect to release them, except for fest-assert 2.0 (a fest-assert 1.5 will be released instead,) in February.

Thanks,

-Alex

On Mon, Jan 21, 2013 at 7:26 AM, Christophe Domas <christop...@gmail.com> wrote:

Hi,

I have the same incompatibility problem between fest-assert-core-2.0M8 and fest-reflect-1.3 (NoClassDefFound on org.fest.util.Iterables).
I want to follow the resolution of these problems (not crucial for me) but I didn't find any issue. Is there any?

regards

To view this discussion on the web visit https://groups.google.com/d/msg/easytesting/-/NRX5mqiEYgoJ.

[Johannes Schneider]

Hi Alex,

at first I want thank you for your work. I really love the FEST libs.

But this blocker hasn't been addressed for several months. A lot of people have reported it, there is a very simple fix (including pull request).

I really can't understand why it takes nearly half a year to fix it (hopefully). I fear that this are those problems that frustrate people and drive them away from using great open source libs.

If you can't find any time to do the release yourself, you should start to think about delegating that work to somebody else. I am sure there are a lot of guys out there that are willing to help you.

Don't get me wrong - of course it is your project and you decide what to do and when.

Regards,

Johannes

[Alex Ruiz]

Johannes, thank you for the kind words and for the patience! :)

I completely messed up by releasing FEST-Assert 2.0 M8. I should have waited to release all libraries at the same time with the updated dependencies, so nobody would suffer the breaking changes I introduced.

I really don't want to have any deprecated code, because it just sits there, bloating the code base. What I'm doing now is working hard to get new versions of all the FEST modules (Swing, Assert 1.x and Reflect) with updated dependencies, without deprecated code and fixing some minor issues.

I expect to have this ready this month (Assert 1.5 and Reflect 2.0 are ready, but better release them with Swing testing as well).

FEST-Assert 2.0 will be released later, because there are some pretty deep changes that need to be done first.

Cheers!

-Alex

To unsubscribe from this group and stop receiving emails from it, send an email to easytesting...@googlegroups.com.

To post to this group, send email to easyt...@googlegroups.com.

Visit this group at http://groups.google.com/group/easytesting?hl=en.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Mark Derricutt]

Could we at least have a 2.0-M9 that works with the new releases ( or
will the unusable M8 now work instead? )

Mark

[Joel Costigliola]

Ok, I have got some time right now and I'm gonna try fixing those annoying incompatibilities ...

As far as I understand things, the problem is that fest-reflect 1.4 can't be used with the fest-util version coming from fest-assert-core 2.0M8 (i.e. fest-util 1.2.3).

It turns out that a lot things have been changed with fest-util 1.2.3 version.

I think that a way to fix the problem is to make fest-assert-core and fest reflect depend on the same fest-util version.
To achieve that we have to release :

• fest-util 1.2.4
• fest-assert-core 2.0M9 which will depend on fest-util 1.2.4
• fest reflect 1.4.1 which will depend on fest-util 1.2.4

I think/hope it should fix Mark, Johannes and Christophe problems, if you have any test cases reproducing your problem, please share them so that I can be sure my solution is fixing them.

I'm gonna explore this solution and if it is not too much work, we will go for it, otherwise we all have to wait for Alex to finish the refactoring is working on and l want to be clear here, this is just a bunch of bugfix releases, Alex major refactoring is our real target.

I will keep you informed whether my solution proposal is reasonably feasible.

Regards,

Joel

--
You received this message because you are subscribed to the Google Groups "easytesting" group.

To unsubscribe from this group and stop receiving emails from it, send an email to easytesting+unsubscribe@googlegroups.com.

[Mark Derricutt]

Working a treat for me so far!

Many cheers!

Joel Costigliola wrote:

I have released :