Automated GUI tests take too long because of doing same steps before the “main test action” can proceed
We are developing a desktop application and I am responsible for GUI testing. Currently we have around 500 tests which take 8 hours to complete.
Is there a way to not use the Observer pattern when creating GUI systems?
In Java, the Swing library implements the Observer/Subscriber-Publisher design pattern to design the way the program responds to events on the GUI (button clicks, etc).
Is there a way to not use the Observer pattern when creating GUI systems?
In Java, the Swing library implements the Observer/Subscriber-Publisher design pattern to design the way the program responds to events on the GUI (button clicks, etc).
Is it good style to store view data inside the model?
I’m using a variant of the MVC pattern. In my GUI code, often the need arises to synchronize “view data” (e.g., selected item) between different views.
Is it good style to store view data inside the model?
I’m using a variant of the MVC pattern. In my GUI code, often the need arises to synchronize “view data” (e.g., selected item) between different views.
Are sequence designs appropriate for GUI button design?
Specifically, I have numerous buttons that will be changing color based on state information from operator input and input from various subcomponents and sensors. I would like to use UML or some other type of design diagrams to be able to capture the color transition.
Where and how to reference composite MVP components?
I am learning about the MVP (Model-View-Presenter) Passive View flavour of MVC. I intend to expose events from view interfaces rather than using the observer pattern to remove explicit coupling with presenter.
Clarification about MVC Design pattern
I’ve been reading up on MVC and I had a doubt. The example where the Model, View and Controller are all individual classes whose objects are created and used to deploy the application in another class. A GUI I’ve designed treats the Model, View and Controller as separate classes and for the most part changes can be made to each without breaking the other .However these separate classes are referenced within the Controller (UI) class. I have no 4th class that calls and creates objects for the Model, View and Controller. Does my setup still follow the MVC design methodology? Thanks.
UI Applications and operations in background threads
I am not really sure about what is the best way to deal with operations executed in background threads in an application I am writing.
Reactive programming vs MVVM pattern for managing GUI updates
Reactive programming and MVVM are two approaches that can address the problem of separating the domain layer from the UI.