Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I'm still relatively new to iOS development and also an absolute stranger to any kind of testing that is not compile, run, and check whatever comes to your mind.
This is obviously a weakness on any developer's profile and I'm decided to get ride of it now that interesting, real projects are coming my way.
In my quest to look for the best approach to go from 0 to 100 as soon (and well) as possible I'm coming to the specialized community to get your feedback.
At the same time I'm asking for your tips I'm also getting into Amazon to look for well-reviewed books on the subject and Google to get the rest. I'm just coming here to gather the feedback of those willing to spare a minute or to so I can probably hit jackpot with a great advise and better plan my learning strategy.
Thats right. For my job testing and test driven development is indispensable.
I often use Java and JUnit, but for Objective-C and XCode I think this screencast is a very good start: http://qualitycoding.org/objective-c-tdd/
Since I watch this screencast I use OCHamcrest and OCMockito (both explaind in this screencast) as well as SenTestingKitAsync for testing asynchronous functions.
I think the Clean Code book is a must have for every developer. There is a chapter about testing.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 9 months ago.
Improve this question
I am using an esp32, with the function esp_https_ota, but i think the situation applies in any iot OTA.
Let's take the situation:
I release a release whose firmware badly controls subsequent OTAs
I would like to release a patch ... but I can't because I broke the OTAs
Are there any tools or best practices to address this?
NB: I am not looking for a "solution", I do not want to remedy a problem that has already occurred, I would simply like to understand good practices.
The easiest way is to work with a beta release; in my devices you can choose a firmware location; the regular and a beta/test location. Last only for devices in reach of course. Will prevent most of the problems.
And the function you intend to I guess is the app rollback function. Although it has some possible security issues, if you run the program and let it do some easy tasks to verify basic function and consequently validate the image, 99% of your problems is solved.
To tackle the last percent I added OTA over SD, so people can put a firmware image on sd card. In my opinion wifi/https takes a lot of buts and ifs to work.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 2 years ago.
Improve this question
For a new developer building an app, are there projects/repositories I can pull into Xcode to study and see how code, files, folders, MVVM patterns are implemented in a BIG project??
It would be great to analyze and refer to a large code-base that has implemented best coding practices for the problem it solves.
This way I (as a new developer) can be aware of how to organize & refactor my code for a maintainable app.
Thank you!
my two cents: don't try to find a large ios code base to study. take a look at smaller, easier-to-consume open source projects and get a feel for what you like / don't like, comparing them against each other. you will find that there is not one set way of doings; if there was, we'd all be doing it! what's important is figuring out what tools / patterns / practices etc. help you build the best app that you can (hint: an app that's built is better than one that's not), and you'll only find that out by doing some building yourself.
There are many open source projects.
First one that comes to mind is Signal.
https://github.com/signalapp
Here are many projects listed by categories:
https://github.com/dkhamsing/open-source-ios-apps
First one that sprung out was Firefox:
https://github.com/mozilla-mobile/firefox-ios
Google should help you find more, just check out your favorite apps and see if they are open source.
Try to find different kinds of projects, with huge storyboards, with many libraries in the Podfile, ...
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I came across https://codeclimate.com.
Super awesome, but I'm working on a project whose code I cannot share with others or Code Climate.
Now I would like to be able to improve my code quality and wonder if anyone can suggest tools that do what codeclimate.com does but locally in development mode, without me having to share my code.
The metric_fu gem seems to be the best option combining all known test tools into 1 an generate a neat report although its not as nice and fully featured as code climate.com
We can use Fog gem which give code complexity at class and method level.
To check code duplications we can use Flay gem.
Both give same result that code climate gives.
Now there's an exact answer: Last year Code Climate released a new platform which includes a command-line interface, Code Climate CLI. It runs entirely on your computer (in a Docker container) and doesn't require a Code Climate account.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
How can I test my Rails app with N concurrent users?
These simulated users will do some actions like upload/download files, etc.
Are there any frameworks or free tools that support this?
ab(Apache Benchmark) is made for that. Here is an example:
https://github.com/igrigorik/async-rails
I use jMeter, although the UI is a little rough IMO. I ended up sharing a lot of code between my easyb (Groovy-based) specs and a mini-DSL I used to create jMeter config/execution files (XML) so redundancy between specs and load testing was reduced. The same should be doable in Ruby as well.
JMeter allows concurrent testing, ramp-ups, all sorts of stuff. I don't know if it does everything a commercial tool does, but I've used it for a long time on a wide range if apps and it's been, more or less, satisfactory.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
My company has been using FogBugz for a while now and we are generally happy with it as a bug-tracking tool. I've been reading Joel Spolsky's articles about their Evidence Based Scheduling feature. It sounds great in theory, but I haven't seen much discussion about how well it actually works in practice. Before I spend a lot of time and effort trying to convince my co-workers to buy in to using it, I'd like to hear from people who have been using this feature in their development.
Have you been using FogBugz' EBS? If so, are you happy with it? Have its estimates been accurate enough to be helpful? With the benefit of hindsight, do you think it was worth the effort to set it up and input all of the information/estimates it requires? Is there some other mechanism that you found that works better?
(Note: I've deliberately posted this to stackoverflow.com rather than fogbugz.stackexchange.com, since I suspect that the user base at fogbugz.stackexchange.com might be unduly biased in favor of FogBugz -- in particular, ex-Fogbugz users who've moved on to something better are unlikely to read or post there)