Mockito VS languagetool

Mockito 5 Released (1 min)🎉 https://github.com/mockito/mockito/releases/tag/v5.0.0

For those using a "release" testBuildType for integration tests, what does your mocking setup look like? My app is stuck on Mockito 2.23.4, because higher (> 1.8.12) versions of Byte Buddy required beyond that point [do not play nicely with non-debuggable APKs](https://github.com/mockito/mockito/issues/2302). Solutions I've considered so far:

Mockito

The code is pretty self explanatory but here's a quick run down. o.getClass().getDeclaredFields() gets us an array of all the fields. We then have a enhanced for loop that loops over the array. Check if the field is annotated field.isAnnotationPresent(Gucci.class). If it is then we set its modifier to true with field.setAccessible(true);. If we don't do this and the field is private we will get an error. Then we get the binary name of the field, field.getGenericType().getTypeName();, remember its just the package and the class name. Lastly we set the value of the field, field.set(o,dynamicInjection(classLoader,binaryName). With that we have now created a dependency injection annotation with the Junit 5 extension model. Now I am sure you can see the tower of exceptions, which is obviously not ideal. I'm not sure how I want to handle all the exceptions yet. However, I will be digging around the Mockito code base to see if I can find how they handle all their exceptions.

Mockito 3.11.* releases

Hi, I've been trying to write parquet files on android for the past couple of days, and have really been struggling to find a solution. My original hypothesis was to just use the java parquet implementation (https://github.com/apache/parquet-mr), but I've since realized that not all java libraries play well with Android. I've gone through essentially dependency hell trying to franken-fit the library into my project, and imported as much as i could before hitting walls such as this one (https://github.com/mockito/mockito/issues/841).

Great tool, thanks for sharing. If you are open to suggestions, I would love to have spellcheck in it.

https://github.com/languagetool-org/languagetool

I don't know of a "global" function, but what you use depends largely on where you're doing your writing. It's possible to spellcheck markdown and html files from a terminal with aspell and to find the correct spelling of partial words with look. Some apps, like Grammarcheck can offer you close to global spellcheck. Apps like LanguageTool offer browser addons to check grammar and spelling.

Proofread for spelling, grammar, and punctuation errors (Grammarly, Hemingway Editor, LanguageTool),

Please re-read the wiki thoroughly, line-by-line, format your resume to the wiki guidelines, verify that each of your bullet points begin with a strong action verb and follow the STAR (Situation, Task, Action, and Result) or XYZ (Accomplished D as Measured by Y, by Doing Z) methods, proofread, revise, and repost your resume.

LanguageTool - I liked using Grammarly to check my writing, but it is not great for privacy considering it sends off everything you write to Grammarly servers. LanguageTool is a great open source alternative that you can run locally.

On extensions, for example, I use LanguageTool [1], which is similar to Grammarly. It could be configured with a local server, although I have a “premium” account which sends data to a 3rd party server. I trust this extension to verify my messages on HN, but I can't trust it to have access to my banking account. This is an example of a really useful extension that I'll never be able to fully trust because it has access to all websites, and it sends all that I write to another server.

In fairness, Firefox's advantage has been that Mozilla has a trustworthy manual review process for the “recommended” extensions.

[1] https://languagetool.org/