3 Configuration 2.0.4 (Quick Reference) Authors: Graeme Rocher, Peter Ledbrook, Marc Palmer, Jeff Brown, Luke Daley, Burt Beckwith Version: 2.3.7 It may seem odd that in a framework that embraces "convention-over-configuration" that we tackle this topic now. With Grails' default settings you can actually develop an application without doing any configuration whatsoever, as the quick start demonstrates, but it's important to learn where and how to override the conventions when you need to. Later sections of the user guide will mention what configuration settings you can use, but not how to set them. 4.1 Basic Configuration For general configuration Grails provides two files: grails-app/conf/BuildConfig.groovygrails-app/conf/Config.groovy Both of them use Groovy's ConfigSlurper syntax. The most basic syntax is similar to that of Java properties files with dot notation on the left-hand side: Note that the value is a Groovy string literal! foo.bar.hello = "world" foo.bar.good = "bye" or by only partially nesting them:
Balsamiq STS Integration This is a quickstart tutorial for the Eclipse Grails support in SpringSource Tool Suite (STS). For more information, see the STS FAQ. For the latest new and noteworthy documents, see the following pages: STS 2.6.0 New and Noteworthy This page is correct for version 2.5.2.RELEASE of STS. In this tutorial, we will look at installation of the tools and creating/importing projects. To begin, install the latest STS, which is freely available for download here. From there, open the dashboard directly, or through the menus Help > Dashboard . Select that tab and the full list of available STS extensions will be shown, which include Groovy and Grails support: There are two grails entries, why two? Let's assume a brand new install here so there is no local copy of Grails on the machine, select 'Grails (current production release)' from the 'Languages and Frameworks' section and 'Grails Support' from the 'Languages and Framework Tooling' section, then click install in the bottom right.
Quality software —12 non functional requirements every app should have If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting! Sharebar When people talk about really great quality software, they usually think in terms of it’s utility, simplicity or aesthetics. Great architecture comes from great constraints How I arrived at this list I started to look at this a little while back when I was putting together our playbook for how we create software for our customers by bringing together agile and user centred design together. Performance This one shouldn’t come as a surprise. 1. How long should your app take to load? 2. Can I get a spinning beachball please? 3. This could be covered off with general reporting times, but if you’re providing an API you should probably consider acceptable query times too. Capacity and Scalability How much do you need to cope with now, and how much do you think you’ll need to cope with in the future. Your audience had better be pretty charmed by you if you can get away with regularly futzing on capacity 4. 5.
Test de performance Un article de Wikipédia, l'encyclopédie libre. Types de Tests[modifier | modifier le code] Ces tests peuvent être de plusieurs types, notamment : Test de charge : il s'agit d'un test au cours duquel on va simuler un nombre d'utilisateurs virtuels prédéfinis, afin de valider l'application pour une charge attendue d'utilisateurs. Si l'application est déjà en production, ou en phase pilote, on peut aussi, afin de connaître les performances du système, réaliser une métrologie, qualifiée de surveillance de la production, qui permettra d'observer dans le détail le fonctionnement du système sur la base d'actions réelles des utilisateurs. Définition du plan de tests[modifier | modifier le code] Le plan de tests est l'expression du besoin de la campagne de tests, et c'est le premier livrable du processus des tests. Les jeux de données permettent de simuler au plus juste la réalité. Présentation des résultats et Bilan des Tests[modifier | modifier le code] Méthodologie[modifier | modifier le code]
InRelease - Agile Release Management for TFS > Home By using Release Management for Visual Studio 2013, your development and operations teams can enable additional capabilities in Team Foundation Server 2013 so that they can more easily and more confidently configure and automate complex deployments to a variety of target environments. You can also model release processes, track approvals and sign-offs, and display release status graphically. Each person using the Release Management Client for Visual Studio 2013 for creating, updating, or deleting a release pipeline sequence must be licensed for either Visual Studio Ultimate with MSDN, Visual Studio Premium with MSDN, Visual Studio Test Professional with MSDN, or MSDN Platforms. To enable the release management capabilities, you must also install the Release Management Server for Team Foundation Server 2013. To model release processes and enable graphical views of release status, you must have the Release Management Client for Visual Studio 2013.
Plugin for Eclipse 3.7(Indigo) Installation Instructions - Google Plugin for Eclipse Vous devez être connecté à Google+ pour effectuer cette opération. Le site Google pour les développeurs a besoin de votre autorisation pour effectuer cette opération. Building Better Software › Using nonfunctional requirements to build better software Understanding nonfunctional requirements — which some people call software quality attributes or nonbehavioral requirements — can make a big difference when you’re building software. But a lot of people have trouble taking a somewhat theoretical idea and applying it to a real-life project. Luckily, we’ve got an easy, practical technique to use nonfunctional requirements on a real software project. How well does your program do… well, whatever it does? I’ve wanted to write a post about nonfunctional requirements for a while. But I’ve been trying to find a good angle for talking about them, because while they can be really practical and useful on a software project, it’s a little hard to get that practicality across in a useful way. Luckily, I’ve been spending a lot of time lately talking about architecture, since Jenny and I are going to give our Beautiful Teams talk at the ITARC New York conference next week. That’s a really subtle point, and it’s a very easy one to overlook.
3 Predictions On The Future Of Enterprise Software Editor’s Note: This guest post is written by Uzi Shmilovici, the founder and CEO of Future Simple, the company behind Base CRM. The first image that comes to my mind when I think about business computing is the dystopic scene from the 1984 Apple commercial: A swarm of employees wearing the same uniforms and marching in unison into their offices where they are forced to use certain devices and software. They sit down in front of their PCs, open a business application their company paid millions of dollars to implement and, in a disciplined manner, fill out forms to populate the company’s database so their managers will be happy. The Anya Major in this dystopic scene is the consumerization of enterprise software. Why is consumerization accelerating? There are three key paradigm shifts that accelerate the consumerization of business software: The devices we use — would you rather use a Dell desktop computer or an iPad? What does this mean for business computing? Image credit Moxiesoft.com
Testability and Entity Framework 4.0 Scott Allen Published: May 2010 Introduction This white paper describes and demonstrates how to write testable code with the ADO.NET Entity Framework 4.0 and Visual Studio 2010. What Is Testable Code? The ability to verify a piece of software using automated unit tests offers many desirable benefits. A good unit test suite allows a development team to save time and remain in control of the software they create. Unit testing comes with a price, however. Microsoft designed the ADO.NET Entity Framework 4.0 (EF4) with testability in mind. The Qualities of Testable Code Code that is easy to test will always exhibit at least two traits. public int Add(int x, int y) { return x + y; } Testing a method is difficult if the method writes the computed value into a network socket, a database table, or a file like the following code. public void AddAndSaveToFile(int x, int y) { var results = string.Format("The answer is {0}", x + y); File.WriteAllText("results.txt", results); } The Repository Pattern