Sep 17, 2015 03:07
"instead I see a rude, disruptive and arrogant team member who does not wish to act in a professional and objective manner." +1
 
Feb 26, 2015 17:02
You shouldn't, but you should know her background before you go on a date :)
Feb 26, 2015 16:56
I am appplying to germany now and I am going through this process of cover letter and so on.
Feb 26, 2015 16:56
Here (in Brazil) we do not have this kind of approach :)
Feb 26, 2015 16:54
I customize my CVs to the employers I am applying, so I can show them I can add value to their business
Feb 26, 2015 16:54
That is a point. It is also a pretty cool career
Feb 26, 2015 16:51
Your issue is that employers are not able to understand what you can do from your resume?
Feb 26, 2015 16:49
@RobertHarvey I am in a similar position. Have you considered a portfolio of projects that you can show employers?
Feb 26, 2015 16:29
No, the feature (test description) is written by the BA. The dev team will implement the tests
Feb 26, 2015 16:28
Sure, @enderland. But as they are written by the business analyst, they are more integration tests than unit tests
Feb 26, 2015 16:26
@RobertHarvey If you could post the reasoning you just had in the question, I would be happy to mark it as an answer
Feb 26, 2015 16:26
Thanks guys for all your help, the community is great :)
Feb 26, 2015 16:26
sure, I will :) But I'm sure this will be a nice first step
Feb 26, 2015 16:24
hm, it makes sense @RobertHarvey
Feb 26, 2015 16:23
@durron597 true, I agree, I just want to avoid errors that are well known by the community :)
Feb 26, 2015 16:20
Or should I do "plain" unit tests, without any kind of behavior description approach?
Feb 26, 2015 16:19
Great, we currently have BDDs as integration tests in our system, in the sense that our BA writes the statements and we implement it.
I do not feel safe because we have no unit tests, and I would like to have them. My question is: how do I create them? Should I write statements similar to the ones the BA write so the behavior of the method itself is described?
Feb 26, 2015 16:17
thanks @MichaelT
Feb 26, 2015 16:16
So, this is what is confusing me. I found in many threads in stackexchange answers similar to this one: http://programmers.stackexchange.com/a/164758/7764 or this one http://programmers.stackexchange.com/a/245746/7764
In which they state that "BDD is not a technology, it is a technique" and that includes unit tests.
Feb 26, 2015 16:12
I'm doing that now
Feb 26, 2015 16:11
Hi guys, nice to see that you are talking about the question I wrote, maybe I can clarify it here
 
Mar 6, 2014 16:21
wow, while I know some of the concepts you talked about, there is a lot to read, so it will take a while, so one last question before I accept this answer (the points in this question will be the best points ever spent here :) ): I would receive the DTOs in my BL. So if I have a method foo() called by 2 views, I will have foo(DTOView1) and foo(DTOview2), each would instantiate a new BO object and populate it and then call the "real" foo(). Correct? This would cause my BL to have many foo's, is this correct?
Mar 6, 2014 16:21
ps: the question was made before I read the links you sent because I would like to clear this and give you the points, then take my time to read everything :)
Mar 6, 2014 16:21
Hey! thanks for the answer. I will read it during the day and get back to you! Tks! One last question (I'm still reading you answer, so sorry if you already answered): Would you agree with w/ @AndrewM when he says that BO should be created on the view layer? If so, how would you solve the issue that my business layer be coupled with my DTO's and, therefore, to my view layer, since DTO's represent the set of information required for a specific view?