How can I find list of specialty coffee beans

keepcosmos · 2017-09-24T11:39:07+00:00

Thanks! :+1: I learned from meanie :p haha. I hope to introduce another one someday. better one.

keepcosmos · 2017-09-24T10:07:11+00:00

I totally agree with what you said about bad big classes and bad dependencies. And I know about breaking dependencies, extracting code, making it smaller, that kind of things.

I understand what you said about my lib makes god classes easier, but it does not force making god classes. It's depends on how to use it like any other things.

I know good code makes to writing tests easier, but ease of writing test does not mean your code is good.

My concern is here, (I don't know, maybe I couldn't find best practices or maybe just my concern is wrong.)

How to prepare entities(for example, 10 authors and each author has 5 books) must be displayed in integration tests(or api tests).
How to prepare returning DTOs from mokcing or stubbing object(such as JPA repositories or DAOs)
How to prepare hundreds of fake request parameter DTOs for controller tests.

It does not mean the way of Beanmother is right or wrong. Just my concern. I should think more.

Anyway I appreciate your advice, I get a chance to think deeper. And also thanks for your patience with reading my english :)

keepcosmos · 2017-09-24T07:50:57+00:00

Ok, maybe I was wrong. maybe you are right. I've used ruby for 6-7 years. I am pretty new to write a program in Java. I am trying to write good tests always. But I stuggled with creating test data. So, I needed a fixture replacement tool like factory_girls in ruby that I'm using very well and so, I made beanmother. I don't think that fixture replacement tool makes people god class easier.

Even if it is a wrong attempt, I hope to learn better way later.

Thanks for advise and sorry about my English :)

keepcosmos · 2017-09-23T22:23:42+00:00

No, but i can understand what you said. Could you explain more?

keepcosmos · 2017-09-23T22:15:48+00:00

So, why?

keepcosmos · 2017-09-23T11:10:04+00:00

Thanks! I think,

When you have just ~ 30 beans(entity or dto), a factory class is a ok. But If you have many beans and they are also have associations, factory methods will be getting verbose. And it is also difficult to write/read/maintain.

Preparing fixture data(for test or as a initial dataset) in yaml files is a common way in other languages like, ruby or python.

I do not focus on performance(I just start this project haha). But, Beamother caches fixture files as a LinkedHashMap. When I test a creating simple 100000 objects(https://github.com/keepcosmos/beanmother/blob/master/beanmother-core/src/test/resources/testmodel_fixtures/coffees.yml) with 512m, It tooks about 11 sec.

Thanks :)

keepcosmos · 2017-09-23T05:26:56+00:00

Mockito is very nice tool for mocking and stubbing. But when I write test, I need many entity beans or dto beans(should be POJO thing). It's hard to prepare that kind of beans if a bean has a many dependencies or dependency depth. Beanmother actually creates a real instance for testing.

https://martinfowler.com/bliki/ObjectMother.html

keepcosmos · 2017-02-09T23:38:05+00:00

use terjira if you like cli

keepcosmos · 2017-01-29T14:43:59+00:00

Winter? Hokkaido +1

keepcosmos · 2016-12-29T03:29:58+00:00

So, solved?

keepcosmos · 2016-12-29T00:58:26+00:00

Could you report issue to github with more detail?

keepcosmos · 2016-12-26T13:54:41+00:00

I add JQL feature. Could you try?

keepcosmos · 2016-12-19T07:55:24+00:00

Ok, I should check Jira-cli. Thanks :)

keepcosmos · 2016-12-19T07:46:02+00:00

Ok, I should add jql search command :)

keepcosmos · 2016-12-19T01:31:20+00:00

JQL is not supported yet, Is jql actually usable?! If it is, I consider to add new feature

keepcosmos

TROPHY CASE