Cached
itself
Group items matching
in title, tags, annotations or url
1More
jmockit - A capable and elegant developer mock testing toolkit for Java - Google Projec... - 0 views
-
"JMockit allows developers to write unit/integration tests without the testability issues typically found with other Mocking APIs. Tests can easily be written that will Mock final classes, static methods, constructors, and so on. There are no limitations. The JMockit Mocking API is simple, consistent, and minimal. There are no special methods or annotations that need to be used in test code, apart from those that really make sense. In general, the use of JMockit APIs for Mocking leads to test code that is better structured and more readable. "
1More
EasyMock - Mock Objects for interfaces & objects by generating them on the fly using Ja... - 10 views
-
"EasyMock provides Mock Objects for interfaces (and objects through the class extension) by generating them on the fly using Java's proxy mechanism. Due to EasyMock's unique style of recording expectations, most refactorings will not affect the Mock Objects. So EasyMock is a perfect fit for Test-Driven Development. EasyMock is open source software available under the terms of the Apache 2.0 license. Development, downloads and issue tracking are hosted on SourceForge. "
1More
http://mockito.org - 0 views
-
Mockito is a Mocking framework that tastes really well. It lets you write beautiful tests with clean & simple API. Mockito doesn't give you hangover because the tests are very readable and they produce clean verification
1More
shared by mikhail-miguel on 12 Jul 23
- No Cached
Code Academy - 0 views
www.codecademy.com
'Recursos de codificação' Recursos de codificação Recursos-de-Codificação WebDev Bookmarks Dev
shared by mikhail-miguel on 12 Jul 23
- No Cached
-
TestLink, Inter Process Communication (IPC), Logo, PySpark, Google Tag Manager, Free IFSC Code, SAP Workflow, Scipy, SAP Hybris, FlexBox, Axure RP, OpenShift, Apache Bench, qTest, TestLodge, Power BI, Jython, Financial Accounting, text and video tutorials for UPSC, IAS, PCS, Civil Services, Banking, Aptitude, Questions, Answers, Explanation, Interview, Entrance, Exams, Solutions, Examples, Online, Quiz, Current Affairs 2017, Aptitude Test, Verbal Ability, General Knowledge, Reasoning, Mock test, Kubernetes, Spring JDBC, Java Concurrency, Spring AOP, Gerrit, Spring MVC, Indian Polity, Histor...
96More
Large scale application development and MVP - Part II - Google Web Toolkit - Google Code - 0 views
-
-
-
@UiHandler("
-
presenter.onAddButtonClicked();
- ...91 more annotations...
-
onAddButtonClicked
-
eventBus.fireEvent(new AddContactEvent());
-
presenter needs to know more about the view
-
view needs to know more about the data model
-
data types are typically homogeneous within column borders
-
ColumnDefinition abstract class
-
houses the any type-specific code (this is the third party mentioned above)
-
ColumnDefinition
-
ColumnDefinition(s) would be created outside of the presenter
-
we can reuse its logic regardless of what view we've attached ourself to
-
update our views such that we can set their ColumnDefinition(s).
-
setColumnDefinitions
-
this.columnDefinitions = columnDefinitions;
-
so that we can pass in
-
a mocked ContactsView instance when testing our ContactsPresenter
-
in our AppController, when we create the ContactsView,
-
new ContactsViewColumnDefinitions().getColumnDefinitions();
-
we can initialize it with the necessary ColumnDefinition(s).
-
contactsView.setColumnDefiniions(
-
-
With our ColumnDefinition(s) we can pass the model untouched.
-
As mentioned above we were previously dumbing down the model into a list of Strings
-
current solution
-
List<String> data
-
display.setData(data);
-
how that data type is rendered.
-
use generics
-
third party that abstracts
-
knowledge of a cell's data type
-
stringing together a list of these classes
-
providing the necessary render()
-
and isClickable()/isSelectable() override
-
ContactsViewColumnDefinitions<ContactDetails>
-
columnDefinitions = new ArrayList<ColumnDefinition<ContactDetails>>()
-
ColumnDefinition<T>
-
ContactsPresenter
-
ContactsViewImpl
-
ColumnDefinition<T> columnDefinition = columnDefinitions.get(j);
-
the presenter can pass the model untouched
-
the view has no rendering code
-
that we would otherwise need to test. And the fun doesn't stop there.
-
presenter.onItemClicked(
-
presenter.onItemSelected
-
ClickEvent
-
cell.getCellIndex()
-
columnDefinition.isClickable()
-
SelectEvent
-
columnDefinition.isSelectable()
-
return shouldFireClickEvent;
-
return shouldFireSelectEvent;
-
respond to user interaction in different ways based upon the cell type that was clicked
-
use them for rendering purposes
-
defining how to interpret user interactions
-
we're going to remove any application state from the ContactsView
-
replace the view's getSelectedRows() with a SelectionModel
-
The SelectionModel is nothing more than a wrapper around a list of model objects.
-
ContactsPresenter holds on to an instance of this class
-
onItemSelected
-
Having the ColumnDefinition create a new widget for each cell is too heavy
-
Replace our FlexTable implementation with an HTML widget
-
calling setHTML()
-
Reduce the event overhead by sinking events on the HTML widget
-
rather than the individual cells
-
update our ContactsView.ui.xml file to use a
-
HTML widget rather than a FlexTable widget.
-
<g:HTML ui:field="contactsTable">
-
Inefficiencies related to inserting new elements via DOM manipulation Overhead associated with sinking events per Widget
-
for each item ask our column definitions to render accordingly
-
each column definition
-
render itself into the StringBuilder
-
rather than passing back a full-on widget
-
calling setHTML on a HTML widget
-
rather than calling setWidget on a FlexTable.
-
This will decrease your load time, especially as your tables start to grow.
-
we're reducing the overhead of sinking events on per-cell widgets
-
instead sinking on a single container
-
ClickEvents are still wired up via our UiHandler annotations
-
get the Element that was clicked on
-
and walk the DOM until we find a parent TableCellElement
-
we can determine the row
-
shouldFirdClickEvent() and shouldFireSelectEvent()
-
to take as a parameter a TableCellElement rather than a HTMLTable.Cell.
-
faster startup times via Code Splitting.
-
runAsync() points
-
split portion of your code is purely segmented
-
not referenced by other parts of the app
-
it will be downloaded and executed at the point that it needs to run
-
Do we really want to download all of that code before the user even logs in?
-
Not really.
-
simply grab the login code, and leave the rest for when we actually need it
-
wrap the code that creates the ContactsView and ContactsPresenter in a runAsync() call
-
as optimizations such as this one become easier and easier to implement.