When I'm working on a project, sometimes I'll design the GUI first and then write the backend code to make it work, but other times I'll do the opposite and make the GUI once I have the system working. How do you choose which way round to code and are there any particular types of project or circumstances that would lean you either way?
In most cases, most people would recommend developing the frontend first. This is especially true if you are talking about a site or application that depends heavily on the user experience. In most cases, it's easier to work the backend to meet the needs of the frontend instead of following the process in reverse.
A GUI is a hierarchical, graphical front-end to a software system that accepts as input user- and system-generated events from a fixed set of events and produces deterministic graphical output.
You need to create something which would let your testers start immediately. Try to think from that prospective.
If they are working on manual UI testing give them a shell of UI with stubs for all the functionality. If there is an interface to be tested make sure it works (even if it returns dummy data) so they could start working with it, etc.
Most of the time it's the UI. You could show it to your users and get immediate feedback which is really useful.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With