Les nouveautés et Tutoriels de Votre Codeur | SEO | Création de site web | Création de logiciel

Seo Master present to you: Post by Michelle Levesque, Google Software Engineer

Today we're unveiling the public release of "Testing on the Toilet": one of Google's little secrets that has helped us inspire our developers to write well-tested code. We regularly write flyers about everything from dependency injection to code coverage, and then plaster the bathrooms all over Google with each episode, almost 500 stalls worldwide.

We've decided to share this secret weapon with the rest of the world to spread our passion to other developers, and to provide a fun and easy way to educate yourself (and the rest of your company) about these important tricks and techniques.

We'll be posting episodes on the brand new Google Testing Blog on a regular basis and providing PDFs so you can print them out and put them up in your own bathrooms, hallways, kitchens, moon bases, secret underground fortresses, wherever. Send your photos and stories to TotT@google.com and let us know how Testing on the Toilet is received at your company.

And meanwhile, keep writing those tests.2013, By: Seo Master
Seo Master present to you:

One of our aims of the Google Analytics Data Export API is to provide access to all the data you find in our reporting UI. To that end, we are releasing 127 new dimensions and metrics via the API today!

Some of the powerful new data points are:

  • Unique visitors - ga:visitors metric has been updated to support the true number of unique visitors for any date range (instead of the daily unique visitors). It also supports significantly more valid combinations.
  • Organic Searches - The number of organic searches within a session.
  • 10 new Adwords dimensions - Including Matched Query (what people searched for, not the bid term) and Placement Domain (which site you content ads were running on).
  • Search Result Views - The number of times a search result page was viewed.
  • 3 Time dimensions - To simplify plotting graphs.

We also included 111 calculated metrics to make it easy to query most common calculations in the reports, such as bounce rate, cost per conversion, and margin. Now, getting calculated metrics is both more convenient and in parity with the calculated metrics in the UI.

You can see a complete list of the new dimensions and metrics in our public changelog.

With all these dimensions and metrics, it can be time consuming to find the values you are looking for. To simplify this, we’re also launching a new interactive dimension and metric search tool. You can use this interactive tool to search for a dimension or metric using its search-as you-type feature. Even more exciting is the ability to easily determine valid dimension-metric combinations just by selecting the dimensions/metrics that you want to request. Here's a screenshot:

We hope that you will find this new tool and additional data useful. As always, we look forward to hearing your feedback, in our developer group.

2013, By: Seo Master
Seo Master present to you: Our friends at Adobe recently started hosting their open source projects on Google Code. We wanted to hear a bit more about their experience moving ActionScript 3 libraries over to Google Code, and here is what they had to say:
The ActionScript Open Source libraries are a set of ActionScript 3 libraries created by Adobe that make it easy to work with online APIs in Flash and Flex applications. There are libraries included for Flickr, YouTube , Mappr, as well as a general utility Library (corelib), a unit testing framework (Flex Unit), as well as a complete library for reading RSS and ATOM feeds.

We recently moved these libraries from our own
Adobe Labs site to Google Code, and have been very happy with the results thus far. The projects were always intended to be community run projects, but our initial deployment site did not have the infrastructure in place to handle hosting an open source project with multiple developers. As the libraries became more and more popular, and as we continued to get requests from developers to improve and contribute code, we decided that we needed to move to a system that would better allow the developer community to contribute to the projects.

We looked at a number of code repositories, but decided on Google Code because it had all of the features that we wanted (Subversion, Issue Tracking, Downloads, Wiki and Groups), and integrated them in a way we felt was intuitive and straightforward. We did run into some initial problems moving the code from our Subversion repository to Google Code, but with some help from Google, were able to make the transition.

We have already seen more participation from the developer community, and have added new features and fixed some bugs. We expect that the projects will continue to grow as more developers start working with ActionScript, Flash and Flex.

Mike Potter, Adobe
2013, By: Seo Master
Powered by Blogger.