Re: Using Mockito with Netbeans

[Vic Ricker]

I can't help with Mockito, except to say that I use it with Netbeans all 
the time.  I write the tests mostly from scratch. I'm not sure what 
Netbeans could automate beyond creating template test methods as it does 
now.


One tip I can share, that I discovered by accident, is that Netbeans can 
show code coverage.  I think the option is hidden if you don't have 
coverage enabled.  We're using jacoco with maven. It will display a 
coverage report for the project and colorize your source files showing 
which lines are covered and not.


 Also, testcontainers is pretty cool for database integration testing.

On 2/29/24 19:56, Leo Donahue wrote:
https://plugins.netbeans.apache.org/?search=Mockito=21= 



On Thu, Feb 29, 2024, 16:43 Greenberg, Gary  wrote:

Yes, I do need to mock CRUD operations without accessing the database.
As I said, code was debugged and tested with the database, but to
comply with the company policy
I do need to add these "fake" unit tests. I haven't used Mockito
for about 10 years and don't want to spend much time
to refresh my knowledge. I do hope that NB have some mocking
features that will help me.

*From:* Leo Donahue 
*Sent:* Thursday, February 29, 2024 1:29 PM
*Cc:* NetBeans Mailing List 
*Subject:* Re: Using Mockito with Netbeans

On Thu, Feb 29, 2024, 13:33 Greenberg,Gary
 wrote:

I already have all DTO and DAO classes written and debugged.
However, per company policy, unit test coverage must be no
less than 75%.
Right now, I have it less than 30%, because this is database
driven project and to comply, I need to create
tests mocking database operations.


>>mocking database operations

Do you mean that you need to mock CRUD in a unit test?

If you create mock data in the test, you control the mock data
which means you're testing a hard coded value or testing for null
and the database is never used.

Is that valuable?

Suppose you unit test pinging the database, as in select something
and it fails because the database is down, or today no permissions
were granted to your test account or your test user password
expired... now what.  The unit test says something is broken but
it may not be in your control.


*From:* Pieter van den Hombergh

*Sent:* Thursday, February 29, 2024 7:49 AM
*Cc:* NetBeans Mailing List 
*Subject:* Re: Using Mockito with Netbeans
generated tests from existing classes sounds like testing
after the fact.

Then I would consider generating the DAOs from information
available, like the database schema or the DTO classes which
should be of the record type.

but if you still insist, make the DAO tests inherit from a
TestBase class that configures the mocked data source.
If the DAO accepts the data source or a connection as
dependency in the injection sense, you are good to go and can
verify the proper use of the dependency by the DAO, which is
the purpose of mocking.

I may find some time tomorrow to come up with a more elaborate
answer.


Kind regards,
Pieter van den Hombergh.


met vriendelijke groet
Pieter van den Hombergh

Op do 29 feb 2024 01:40 schreef Greenberg, Gary
:

I am quite used to generate unit tests for my code using
Netbeans Tools->Create/Update Tests. JUnit is great.
However, now I need to create tests for some DAO classes
where I will need to mock database access.
I plan to use Mockito for that.  Does Netbeans have any
features automating Mockito test creation?

*Gary Greenberg*

Staff Software Engineer

Re: Using Mockito with Netbeans

[Leo Donahue]

https://plugins.netbeans.apache.org/?search=Mockito=21=

On Thu, Feb 29, 2024, 16:43 Greenberg, Gary  wrote:

> Yes, I do need to mock CRUD operations without accessing the database.
> As I said, code was debugged and tested with the database, but to
> comply with the company policy
> I do need to add these "fake" unit tests. I haven't used Mockito for about
> 10 years and don't want to spend much time
> to refresh my knowledge. I do hope that NB have some mocking features that
> will help me.
> --
> *From:* Leo Donahue 
> *Sent:* Thursday, February 29, 2024 1:29 PM
> *Cc:* NetBeans Mailing List 
> *Subject:* Re: Using Mockito with Netbeans
>
>
> On Thu, Feb 29, 2024, 13:33 Greenberg,Gary 
> wrote:
>
> I already have all DTO and DAO classes written and debugged.
> However, per company policy, unit test coverage must be no less than 75%.
> Right now, I have it less than 30%, because this is database driven
> project and to comply, I need to create
> tests mocking database operations.
>
>
> >>mocking database operations
>
> Do you mean that you need to mock CRUD in a unit test?
>
> If you create mock data in the test, you control the mock data which means
> you're testing a hard coded value or testing for null and the database is
> never used.
>
> Is that valuable?
>
> Suppose you unit test pinging the database, as in select something and it
> fails because the database is down, or today no permissions were granted to
> your test account or your test user password expired... now what.  The unit
> test says something is broken but it may not be in your control.
>
> --
> *From:* Pieter van den Hombergh 
> *Sent:* Thursday, February 29, 2024 7:49 AM
> *Cc:* NetBeans Mailing List 
> *Subject:* Re: Using Mockito with Netbeans
>
> generated tests from existing classes sounds like testing after the fact.
>
> Then I would consider generating the DAOs from information available, like
> the database schema or the DTO classes which should be of the record type.
>
> but if you still insist, make the DAO tests inherit from a TestBase class
> that configures the mocked data source.
> If the DAO accepts the data source or a connection as dependency in the
> injection sense, you are good to go and can verify the proper use of the
> dependency by the DAO, which is the purpose of mocking.
>
> I may find some time tomorrow to come up with a more elaborate answer.
>
>
> Kind regards,
> Pieter van den Hombergh.
>
>
> met vriendelijke groet
> Pieter van den Hombergh
>
> Op do 29 feb 2024 01:40 schreef Greenberg, Gary  >:
>
> I am quite used to generate unit tests for my code using Netbeans
> Tools->Create/Update Tests. JUnit is great.
> However, now I need to create tests for some DAO classes where I will need
> to mock database access.
> I plan to use Mockito for that.  Does Netbeans have any features
> automating Mockito test creation?
>
> *Gary Greenberg*
>
> Staff Software Engineer
>
>
>
>

Re: Using Mockito with Netbeans

[Greenberg, Gary]

Yes, I do need to mock CRUD operations without accessing the database.
As I said, code was debugged and tested with the database, but to comply with 
the company policy
I do need to add these "fake" unit tests. I haven't used Mockito for about 10 
years and don't want to spend much time
to refresh my knowledge. I do hope that NB have some mocking features that will 
help me.

From: Leo Donahue 
Sent: Thursday, February 29, 2024 1:29 PM
Cc: NetBeans Mailing List 
Subject: Re: Using Mockito with Netbeans


On Thu, Feb 29, 2024, 13:33 Greenberg,Gary  wrote:
I already have all DTO and DAO classes written and debugged.
However, per company policy, unit test coverage must be no less than 75%.
Right now, I have it less than 30%, because this is database driven project and 
to comply, I need to create
tests mocking database operations.

>>mocking database operations

Do you mean that you need to mock CRUD in a unit test?

If you create mock data in the test, you control the mock data which means 
you're testing a hard coded value or testing for null and the database is never 
used.

Is that valuable?

Suppose you unit test pinging the database, as in select something and it fails 
because the database is down, or today no permissions were granted to your test 
account or your test user password expired... now what.  The unit test says 
something is broken but it may not be in your control.


From: Pieter van den Hombergh 
mailto:pieter.van.den.hombe...@gmail.com>>
Sent: Thursday, February 29, 2024 7:49 AM
Cc: NetBeans Mailing List 
mailto:users@netbeans.apache.org>>
Subject: Re: Using Mockito with Netbeans

generated tests from existing classes sounds like testing after the fact.

Then I would consider generating the DAOs from information available, like the 
database schema or the DTO classes which should be of the record type.

but if you still insist, make the DAO tests inherit from a TestBase class that 
configures the mocked data source.
If the DAO accepts the data source or a connection as dependency in the 
injection sense, you are good to go and can verify the proper use of the 
dependency by the DAO, which is the purpose of mocking.

I may find some time tomorrow to come up with a more elaborate answer.


Kind regards,
Pieter van den Hombergh.


met vriendelijke groet
Pieter van den Hombergh

Op do 29 feb 2024 01:40 schreef Greenberg, Gary :
I am quite used to generate unit tests for my code using Netbeans 
Tools->Create/Update Tests. JUnit is great.
However, now I need to create tests for some DAO classes where I will need to 
mock database access.
I plan to use Mockito for that.  Does Netbeans have any features automating 
Mockito test creation?


Gary Greenberg

Staff Software Engineer

Re: Using Mockito with Netbeans

[Leo Donahue]

On Thu, Feb 29, 2024, 13:33 Greenberg,Gary 
wrote:

> I already have all DTO and DAO classes written and debugged.
> However, per company policy, unit test coverage must be no less than 75%.
> Right now, I have it less than 30%, because this is database driven
> project and to comply, I need to create
> tests mocking database operations.
>

>>mocking database operations

Do you mean that you need to mock CRUD in a unit test?

If you create mock data in the test, you control the mock data which means
you're testing a hard coded value or testing for null and the database is
never used.

Is that valuable?

Suppose you unit test pinging the database, as in select something and it
fails because the database is down, or today no permissions were granted to
your test account or your test user password expired... now what.  The unit
test says something is broken but it may not be in your control.

--
> *From:* Pieter van den Hombergh 
> *Sent:* Thursday, February 29, 2024 7:49 AM
> *Cc:* NetBeans Mailing List 
> *Subject:* Re: Using Mockito with Netbeans
>
> generated tests from existing classes sounds like testing after the fact.
>
> Then I would consider generating the DAOs from information available, like
> the database schema or the DTO classes which should be of the record type.
>
> but if you still insist, make the DAO tests inherit from a TestBase class
> that configures the mocked data source.
> If the DAO accepts the data source or a connection as dependency in the
> injection sense, you are good to go and can verify the proper use of the
> dependency by the DAO, which is the purpose of mocking.
>
> I may find some time tomorrow to come up with a more elaborate answer.
>
>
> Kind regards,
> Pieter van den Hombergh.
>
>
> met vriendelijke groet
> Pieter van den Hombergh
>
> Op do 29 feb 2024 01:40 schreef Greenberg, Gary  >:
>
> I am quite used to generate unit tests for my code using Netbeans
> Tools->Create/Update Tests. JUnit is great.
> However, now I need to create tests for some DAO classes where I will need
> to mock database access.
> I plan to use Mockito for that.  Does Netbeans have any features
> automating Mockito test creation?
>
> *Gary Greenberg*
>
> Staff Software Engineer
>
>
>
>

Re: Missing nb-javac plugin in NetBeans IDE 21

[Geertjan Wielenga]

The Apache NetBeans 21 binary releases require JDK 11+, and officially
supports running on JDK 11, 17 and 21.


On Thu, 29 Feb 2024 at 16:05, Ulf Zibis  wrote:

>
> Am 29.02.24 um 21:51 schrieb Ulf Zibis:
>
> Hi,
>
> when I start the IDE, I get this message:
>
> Oups, after I hit Install, nothing more happens
>
> When I hit Install, a new dialogue asks for confirmation. After
> confirmation of the dialogue and "Restart IDE" I again get the same message.
>
> This happens when I try to activate the Java SE plugin. After restart, I
> again get the message of missing nb-javac and the Java SE plugin is still
> not activated. I tried several times, also with canceling the first
> dialogue. Nothing helps.
>
> What I'm doing wrong?
>
> -Ulf
>
>

Re: Missing nb-javac plugin in NetBeans IDE 21

[Ulf Zibis]

Am 29.02.24 um 21:51 schrieb Ulf Zibis:


Hi,

when I start the IDE, I get this message:


Oups, after I hit Install, nothing more happens


When I hit Install, a new dialogue asks for confirmation. After confirmation of the 
dialogue and "Restart IDE" I again get the same message.

This happens when I try to activate the Java SE plugin. After restart, I again 
get the message of missing nb-javac and the Java SE plugin is still not 
activated. I tried several times, also with canceling the first dialogue. 
Nothing helps.


What I'm doing wrong?

-Ulf

Re: Missing nb-javac plugin in NetBeans IDE 21

[Ulf Zibis]

Am 29.02.24 um 21:51 schrieb Ulf Zibis:


Hi,

when I start the IDE, I get this message:


I'm running NetBeans IDE 21 on Ubuntu 22.04 with openjdk-18-jdk.

-Ulf


-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Missing nb-javac plugin in NetBeans IDE 21

[Ulf Zibis]

Hi,

when I start the IDE, I get this message:

When I hit Install, a new dialogue asks for confirmation. After confirmation of the 
dialogue and "Restart IDE" I again get the same message.

What I'm doing wrong?

-Ulf

Re: Using Mockito with Netbeans

[Greenberg, Gary]

I already have all DTO and DAO classes written and debugged.
However, per company policy, unit test coverage must be no less than 75%.
Right now, I have it less than 30%, because this is database driven project and 
to comply, I need to create
tests mocking database operations.

From: Pieter van den Hombergh 
Sent: Thursday, February 29, 2024 7:49 AM
Cc: NetBeans Mailing List 
Subject: Re: Using Mockito with Netbeans

generated tests from existing classes sounds like testing after the fact.

Then I would consider generating the DAOs from information available, like the 
database schema or the DTO classes which should be of the record type.

but if you still insist, make the DAO tests inherit from a TestBase class that 
configures the mocked data source.
If the DAO accepts the data source or a connection as dependency in the 
injection sense, you are good to go and can verify the proper use of the 
dependency by the DAO, which is the purpose of mocking.

I may find some time tomorrow to come up with a more elaborate answer.


Kind regards,
Pieter van den Hombergh.


met vriendelijke groet
Pieter van den Hombergh

Op do 29 feb 2024 01:40 schreef Greenberg, Gary :
I am quite used to generate unit tests for my code using Netbeans 
Tools->Create/Update Tests. JUnit is great.
However, now I need to create tests for some DAO classes where I will need to 
mock database access.
I plan to use Mockito for that.  Does Netbeans have any features automating 
Mockito test creation?


Gary Greenberg

Staff Software Engineer

Re: Using Mockito with Netbeans

[Pieter van den Hombergh]

generated tests from existing classes sounds like testing after the fact.

Then I would consider generating the DAOs from information available, like
the database schema or the DTO classes which should be of the record type.

but if you still insist, make the DAO tests inherit from a TestBase class
that configures the mocked data source.
If the DAO accepts the data source or a connection as dependency in the
injection sense, you are good to go and can verify the proper use of the
dependency by the DAO, which is the purpose of mocking.

I may find some time tomorrow to come up with a more elaborate answer.


Kind regards,
Pieter van den Hombergh.


met vriendelijke groet
Pieter van den Hombergh

Op do 29 feb 2024 01:40 schreef Greenberg, Gary :

> I am quite used to generate unit tests for my code using Netbeans
> Tools->Create/Update Tests. JUnit is great.
> However, now I need to create tests for some DAO classes where I will need
> to mock database access.
> I plan to use Mockito for that.  Does Netbeans have any features
> automating Mockito test creation?
>
> *Gary Greenberg*
>
> Staff Software Engineer
>
>
>