I've just been tasked with finding automated actionscript frameworks. Can anyone offer the best out there? I'm just beginning to write the code for my project. Is it better for me to keep my MXML and AS in separate files so I can more easily integrate with any frameworks....or does it even matter?
Thanks for any helpful tips!
FlexUnit is a good unit testing framework.
For continuous integration, I've used jenkins, maven, flex-mojos. That will require a bit more work to setup, but it is well worth the effort.
If you need functional testing, I haven't used it myself, but I have heard that Flex Monkey is pretty good.
I'm a big fan of AsUnit I've used it in combination with both Hudson build manager and TeamCity with great results
Related
I'm looking for a robust and efficient method of creating any kind of imaginable control to use with a LabVIEW project. I'm curious what you've tried and what the pros and cons are. I myself have never used LabVIEW, but have been approached to write controls for it based on my knowledge of other things (C#, HTML5, Flash, Silverlight, etc).
It appears to me as though this kind of thing has been or can be done in .NET, Flash, WebGL, Qt, Silverlight, and maybe some others as well. Ideally, we don't want to have to write any code twice, so platform flexibility is a great thing, which makes me lean toward a web solution. But ease of implementation is important as well, and I would think a web solution would require some extensive web services parsing and programming every time a control is going to be used. But I could be wrong. An eye on the future is also important. If something would be a great solution today, but probably worthless in 2 years, no point in bringing it up.
(Please realize that I am NOT simply asking how to change the colors of (customize) a LabVIEW control, nor am I interested in xControls as the final solution as apparently they aren't robust enough.)
Thanks in advance!
I am aware that this probably doesn't answer your question, but if you have access to LabVIEW, you could analyse the "Military" Theme Custom Control Suite, and look at examples on the UI Interest Group and LabVIEW UI Tips and Tricks. That's probably the best you could do with LabVIEW.
.NET is probably your best bet, LabVIEW supports .net controls, so you can define the UI and reuse your .net code.
I have heard rumours that the new LabVIEW version (2013 due in September) will use .NET 4 libraries as the default instead of the current 2, so you might want to keep that in mind.
I wouldn't ditch XControls that easily if I was your company (I can understand it's not your cup of tea).
I am working in an enterprise with some legacy applications, which are quite coupled.
Integration test is thus very important. I am looking for a distributed testing framework, or a combination of them that QA team and development team can both leverage on. For "distributed" I refer to the many environments for testing, while a single application itself is not a distributed system.
The following criteria might not be the ideal model, but kind of requirement and expectation of the tool to be developed.
Such framework should be :
open sourced
community support to learn, maintain and extend :)
distributed
allow tests to be execute in multiple environments.
since test cases may change quite often, it should be managable to distributed those test into target machines with target codebase to run.
I am checking out [STAF][1] on this.
allow integration tests
I am looking into Camel testing. we have some existing "simulator", "mock" to stimulate some applications behavior.
framework with easy-to-use dependency injection / mock will be very helpful..
with WEB UI, wich is a single place that can
- all testing results are shown
- able to trigger test
- able to see testing definition
Human readable and configurable acceptance testing definition
Testing language should be in a readable DSL
I wonder is framework like FitNesse a good choice as I did not figure out a way to test it distributed.
For Citrus I am concerning XML is hard to read
Some current frameworks
My team has been suggesting JSystem, while it is possible to distribute tests, there is no web GUI and
my major concern is its development has been stopped since 2009
I looked into many frameworks as mentioned,
Grinder - seems better suite web load testing?
JMeter- this seems to be closer, but also focused on load test?
more on background: most developers are familiar with JAVA and currently we use Hudson to run JUnit tests.
And finally I am also thinking a more conceptual issue, should xUnit test, integration test, acceptance test all being separated? xUnit test should be stick with code base? perhaps this worth another question, but with that in mind I am not sure I am looking for the right thing.
I will greatly appreciate if you can give me some comments on the thought / suggest some frameworks. Thanks a lot in advance.
I will suggest you to use Jenkins Framework.
Open source
Can be used for different environments
I myself working over Integration Testing using Jenkins so suggest you for this.
Web UI is very interactive.
Large variety of plugins is available and development is still on.
Write some ANT, MAVEN scripts you can get your job done through this.
I'm looking for a build tool (such as ant, maven, make, etc.) that uses JSON-based configuration files?
Does such a tool exist?
Nokia/Qt just announced their "QBS" build system, which is JSON-based, and is actually a build engine intended for easy adoption by IDEs (a principal reason for adopting JSON).
Introducing qbs
Rather than a "pre-make" generator of Makefiles/vcprojs/etc. (like CMake and QMake, etc.), qbs is intended to actually be the build engine.
Google turned up Gaudi though it is still in the early phases.
I think what you're really looking for is a build tool that doesn't force you to configure everything in XML?
In that case your best bet is Gradle. It doesn't have the same sort of adoption as ANT or Maven, but does have the advantage of learning lessons from both.
I would advise you to beware of straying from standard build tooling... It makes life tougher for others attempting to build your code. This is something Gradle solved by providing a build wrapper.
I'm trying to get a few web development ideas off the ground. Unfortunately I will be the only developer, so I'm focusing on getting a good debuggable, testable setup going that I can develop applications rapidly with.
Which languages, development styles and frameworks would you recommend for rapid development? Last time I checked RoR was the next big thing but that was a while back.
Ruby on Rails is a good choice for rapid prototyping. It's simple, clean and easily learned. PHP also offers a fairly low learning curve and a wide variety of built-in functionality for accomplishing most tasks. Both languages have their shortcomings, but on small-team projects for low to moderate traffic sites, you aren't likely to bump up against them.
The one you know best.
For people who are comfortable with Python there's also Django.
I guess it is pretty much an equivalent to Ruby on Rails (although I never used Ruby on Rails). Django's concept is to have many autonomous applications which can be used together in order to build small to large scale websites. It has great documentation, although deployment can be quite a hassle. Unfortunately it's not supported by many hosters.
PHP with Zend Framework has comparetively lower development time.
If you are familiar with C# or VB.NET and HTML then ASP.NET is also a very good option.
Just to add another, GWT (Google Web Toolkit) is an awesome option. It allows you to write all of your code in one language (more or less, you'll still need a bit of css --for the record ASP.NET allows this as well) and you can create really rich applications with all kinds of awesome javascript and ajax stuff without needing to know javascript. Their tutorials are great and personally, I think you can get off the ground really, really quickly.
I guess it matters more as to what languages you're most familiar with.
Whatever that language is, look for a good MVC framework for it.
As a new developer, is GAIA Framework something that I want to look into. Is this going to stifle my learning and keep me dependent upon such.
What are the limitations of this framework. Is there another framework out there that you can suggest for rapid site development with deep-linking and the other bells and whistles?
Thanks!
As a new developer, there's a good chance that you'll write better code if forced to by a structured framework like Gaia. Building Flash websites can be a tricky ordeal unless you're well versed in Flash and Actionscript.
I'd say give it a try and see if you like it. Gaia should save you some time once you understand it. Whenever I try a new framework, I try to build a sample project or two just to get the hang of it before I actually use it on a real project.
If you're new to Flash, Gaia could also be a good tool to learn a decent workflow between your design and code and just in general when it comes to Flash.
If you dig into the code and try to figure out how things are done and why they're done that way, I don't really see Gaia impeding your learning.
It all depends on how you use Gaia. If you use Gaia to make a website then pick apart the created code and figure out how it did the things it did then it will help you learn immensely.
On the flip side if you just publish websites using it and don't bother to pick it apart to learn the internals then it will simply be a crutch allowing you to never learn how to do it yourself. An ability to create something that you could not have otherwise created, and if you cannot use it again in the future, you will not have any clue of how to do it.
Use it as a learning tool, not just a building tool.
EDIT: That was all general comment on building tools in general. Specifically relating to Gaia I'd like to add that personally I think most top end devs make their websites MUCH MUCH better than the Gaia framework does. As a matter of personal opinion I'd only recommend using it as a base learning tool, then building your own framework that you can constantly improve on as you get better.
I have used it in several projects. My experience is that some things are really easy to do with GAIA, and some things are hard because you need to stick to the structure.
It also depends on what type of project you are creating. I think it is worth a try, because you can learn a lot from the structure and methods that the GAIA team created.