Google I/O offered 80+ sessions featuring technical content on Google Wave, Android, App Engine, Chrome, Google Web Toolkit, AJAX APIs, and many more. The available session videos and slides from each track are listed below.
Posted in Google.
– June 13, 2009
Recently, I take the error “The folder path ‘C:’ contains invalid character” when I try to install iTunes 8.1 to my Vista box.
I get rid of this error by following the steps below. It worked for me. Hopefully, it works for you.
- Open the registry editor by using the command “regedit” from the “Run” window.
- Go to “HKEY_LOCAL_MACHINE–>SOFTWARE”
- Delete “Apple Computer, Inc.” and “Apple Inc.” items
- Try to reinstall iTunes.
And, ladies and gentlemen, please welcome, The iTunesssss (It’ll be nice to give an explosion sound effect in the background. )
Posted in Apple.
– April 12, 2009
Continuous Integration (CI) is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily – leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly.
At a high level, the value of CI is to:
- Reduce risks
By integrating many times a day, you can reduce risks on your project. Doing so facilitates the detection of defects, the measurement of software health, and a reduction of assumptions.
- Reduce repetitive manual processes
Reducing repetitive processes saves time, costs, and effort.
- The process runs the same way every time.
- An ordered process is followed. For example, you may run inspections (static analysis) before you run tests—in your build scripts.
- The processes will run every time a commit occurs in the version
- Generate deployable software at any time and at any place
CI can enable you to release deployable software at any point in time. From an outside perspective, this is the most obvious benefit of CI. With CI, you make small changes to the source code and integrate these changes with the rest of the code base on a regular basis. If there are any problems, the project members are informed and the fixes are applied to the software immediately.
- Enable better project visibility
CI has the following positive effects.
- Effective decisions: A CI system can provide just-in-time information on the recent build status and quality metrics.
- Noticing trends: Since integrations occur frequently with a CI system, the ability to notice trends in build success or failure, overall quality, and other pertinent project information becomes possible.
- Establish greater confidence in the software product from the
Overall, effective application of CI practices can provide greater confidence in producing a software product. With every build, your team
knows that tests are run against the software to verify behaviour, that
project coding and design standards are met, and that the result is a
functionally testable product.
 Continuous Integration by Martin Fowler
 Continuous Integration: Improving Software Quality and Reducing Risk by Paul Duvall, Steve Matyas and Andrew Glover
Posted in Agile, Software Engineering.
– March 7, 2009
After two weeks experience with iPhone 3G, I decided to share some free applications that I liked most. Here is the list:
- Evernote [iTunes Link]: Evernote for iPhone (and iPod Touch) lets you capture any moment or idea as it happens, wherever you may find yourself. And, thanks to Evernote’s amazing cloud-based sync, you can recall it all any time from your iPhone, Mac, PC, the Web, or other mobile device.
- Create and edit new notes on the fly
- Snap a photo right into your account
- Record a quick voice memo
- Easily access all of your notes
- Select notes for offline viewing
- Wikipanion [iTunes Link]: “Wikipanion is the best and fastest Wikipedia browsing application for the iPhone”. It is designed for easy, search, navigation and display of Wikipedia entries. Streamline your browsing with history grouped by visit date, and bookmarking that not only bookmarks individual entries but individual sections within an entry.
- Fast: Wikipanion uses a direct connection to the Wikipedia servers, making it extremely fast.
- Smart: Wikipanion understands the page. Wikipanion pulls out meta material from the page, understanding sections and related foreign language pages.
- Convenient: Wikipanion meshes the Wikipedia with your iPhone. Get automatic search results while you type. Set your own font size that is saved and applied to every page with no future adjustment. Your last visited page is opened up from when you last left the application.
- International: Wikipanion goes international. Set a primary search language. Switch between different language versions of the page. Quickly retry an existing search in another language.
- Facebook [iTunes Link]: Facebook for iPhone makes it easy to stay connected and share information with your friends. Use your iPhone to start a conversation with Facebook Chat, check your friends’ latest photos and status updates, look up a phone number or upload your own mobile photos to Facebook while on go.
- The full news feed
- News feed story comments
- People search
- Friend requests
- Photo tagging
- Photo captioning
- Photo posts to your friends’ Wall
- Your entire inbox, plus the sent folder and updates tab
- Inbox search
- Message attachments
- Airme [iTunes Link]: Airme lets you capture the moment with your iPhone camera and instantly share it with your friends and family. Airme currently supports:
You can take most photo sizes and include your own custom tags or use the built in popular tag lists. Landscape and portrait photos are supported.
- Dictionaire [iTunes Link]: Dictionaire is an easy to use, no fluff dictionary app for your iPhone. Helps you find words when you need to.
- 140,000 definitions
- Helps you find words that “sound like” others
- Short, simple definitions
Enjoy your applications.
Posted in iOS.
– November 30, 2008
I had a conversation with my friend as follows:
- How can I run my unit tests in some specific order Çetin? I need to execute them in order, otherwise some of my tests fail.
- Unit tests must be “independent”. So, you don’t need any order in fact and you can’t guarantee it also.
I tried to explain him why they must be independent shortly. After this conversation, I opened my unit test reference book (Pragmatic Unit Testing in Java with JUnit) and looked again the properties of good unit tests to refresh my memory. Let’s remember them together briefly:
Unit tests need to be run automatically. Invoking one more unit tests can’t be any more complicated than pressing one button in the IDE or typing in one command at the prompt.
Don’t introduce a test that breaks the automatic model by requiring manual steps. Think about a man sitting in front of the machine waiting for popups to confirm. It is not we want. Whatever test requires (database, network connection etc.) make these an automatic part of the test.
A machine should be running all of the unit tests for all checked-in code continuously. This automatic check ensures that whatever is checked-in hasn’t broken any test, anywhere. Investigate systems such as Cruise Control, Hudson, Teamcity, Anthillpro, Apache Continuum etc.
Test must determine for itself whether it passed or failed. It means you don’t have to think about it. No one needs to read the test results to check whether the code is working or not.
Good unit tests are thorough; they test everything that’s likely to break. But just how thorough? Every line of code, branch, exception or most likely candidates for error like boundary conditions, missing and malformed data, and so on. It’s a question of judgment, based on the needs of your project (time, effort, budget). If you want to aim for more complete coverage, then you may want to invest in code coverage tools (EMMA, Cobertura, Clover etc.) to help.
The goal is that every test should be able to run over and over again, in any order, and produce the same results every time. This means that tests cannot rely on anything in the external environment that isn’t under your direct control.Use mock objects (JMock, EasyMock, JMockit, and so on) as necessary to isolate the item under test and keep it independent from the environment.
Each test should produce the same results every time. If it doesn’t, then that should tell you that there’s a real bug in the code.
Tests need to be kept independent from the environment and each other. Make sure you’re only testing one thing at a time. It doesn’t mean that you use only one assert in a test, but that one test method should focus on a method, or a small set of production methods that, together, provide some feature.
Independent also means that no test relies on any other test; you should be able to run any individual test at any time, and in any order. You don’t want to have to rely on any other test having run first. Use per-test and per-class setup/teardown methods to get a fresh start.
The code you write for a unit test is real. This means that it must be written and maintained to the same professional standards as your production code. You write lots of test code (as much as real code) therefore, test code needs to be kept neat and tidy, well designed and well-factored, just as professional as the production code.
So, a-trip always makes you feel good.
Source: Pragmatic Unit Testing in Java with JUnit
Posted in TDD.
– October 25, 2008