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 9 years ago.
Improve this question
I am a native Dutch speaker, and we refer to the different environments for production, staging etc. as "OTAP"
Ontwikkeling - Development
Test - Testing
Acceptatie - Acceptance / Staging
Productie - Production.
I would like to know if there is a similar acronym/standard naming scheme in English? It is hard to google, as I do not know the proper words to search for (otherwise I wouldn't be asking this question :))
I am also a native Dutch speaker. OTAP is the Dutch translation of DTAP (development, test, acceptance, production). Although there is not much concencus regarding naming schemes I currently use the following naming (much like what you suggested) for web development:
development.domain.tld (for local development, though domain.dev is used a lot as well)
test.domain.tld (for testing)
acceptance.domain.tld (for customer acceptance)
domain.tld (live site)
the acceptance site is usually misused as a staging environment as well.
When it was not related to web applications or web sites we used to refer to the type of test (SAT: site acceptance test, FAT: factory acceptance test and sometimes IAT: integration stage if more companies work on one project).
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 8 years ago.
Improve this question
How is STAF better than compared to Jenkins + plugins in CI, testing and deployment?
Jenkins is able to achieve automated testing and deployment using plugins, then in what situations should one use a framework like STAF?
Maybe I'm wrong, but these two are just two different things. While STAF is
multi-platform, multi-language framework designed around
the idea of reusable components, called services
the Jenkins is
extendable continuous integration server
I assume that you accept their concept to be leveraged to help solve common development problems, such as more frequent product cycles, less preparation time, reduced testing time, more platform choices, more programming language choices, and increased Language requirements.
I think that both can help in these areas since they are a proven and mature technologies, which promote automation and reuse. Also have broad platform and language support, and provides a common infrastructure across teams.
How you'll use them in order to achieve these goals - it's up to you. And why not combine them - JENKINS STAF+STAX Plugin
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 9 years ago.
Improve this question
What is the difference between Installation Testing and Compatibility Testing in context of software Testing ?
Terminology in test is not something that is engraved somewhere and identical for everyone.
Nevertheless, my understanding would be:
installation testing : testing the download, deploy and set-up and the Software. Test with different initial configurations (soft never installed before, soft installed and removed, soft here and we want to upgrade etc.).
compatibility testing: testing the global behavior of your product (not just the install, but you would have to include it) on different platforms. Depending on your product and you are supposed to support, you will make variation on hardware, OS, browsers, databases etc.
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
I've been trying to describe the concept of platforms to some non-developer people on my team. I'm trying to explain how platforms are more than just tools and environments. For example, the Facebook Platform. How to describe the fact that the platform is more than just the website, but includes protocols like XFBML, opengraph, etc.
Facebook Platform is one example, but I would be interested if anyone has an abstracted way to describe what 'platforms' are in the tech world. I've had difficulty explaining this concept before in situations unrelated to flash.
Analogies that aren't tech related would be helpful as well.
I would say something about it being all-inclusive and extending to include all functionality that the entire ecosystem around that particular piece of software needs to thrive.
The Wikipedia page might help in putting it into words: http://en.wikipedia.org/wiki/Computer_platform
I use a "restaurant" metaphor, myself: Think of the kitchen, the bar, the dining room as components to the platform. How the decor can change in the dining room without changing the function, but can affect how customers perceive the business. How the recipes instruct the cooks, and the interactions with the wait staff can all affect different aspects of the business much like different pieces of your platform can be modified to affect different aspects of your business. Oh, and don't forget management!
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I am looking to get a comparison between stress testing tools that are available today. The options put forward to us are either VSTS or Loadrunner.
As of now, the inclination is towards Loadrunner, but we are looking to see if there is any better option today.
Depends on what you're testing. Static HTTP or simple JSP pages, use something free like jmeter. If you're testing ASP.net, silverlight or other MS technology stack apps, then VSTS is your best bet. For almost anything else LR works well, including newer Rich Internet Web 2.0 type pages including AJAX and Flex.
Loadrunner licenses are prohibitively expensive, if you're looking at a one off test, it isn't worth acquiring a license.
For .NET Apps you can rely on VSTS. They help you simulate
Web Services Performance Testing
Coded UI for functional testing
Xpath Testing
patterns & practices: Performance Testing Guidance
http://perftesting.codeplex.com/wikipage?title=How%20To%3A%20Use%20Data%20Binding%20in%20Load%20Tests%20in%20Microsoft%20Visual%20Studio%20Team%20System&ProjectName=perftesting
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I work for a insurance company. We have our own development department made-up of almost 150 people plus some providers (outsourcing and custom made apps pretty much). In our company my team have made what we call non-functional logic libraries. That is, software libraries to handle things that are horizontal to all the development teams in our department, e.g. Security, Webservices, Logging, Messaging and so on. Most or these tools are either made from scratch or adaptation of a de-facto standard. For example our logger is an appender based on Log4J that also saves the logging messages into a DB. We also define what libraries to use in the application, for example which framework for webservices to use. We use pretty much JavaEE and Oracle AS in all our organization (with some Websphere Application servers).
Much of these projects have their architecture documented (use cases, UML diagrams, etc) and generally the generated documentation are available.
Now what we have seen is that for users sometimes is difficult to use the the libraries we provide and the are constantly asking question or they simply don't use them.
So we are planning to generate a more friendly documentation for them, so my question is:
What are the best practices or the checklist that software documentation should have?
Something comes to my mind:
API Reference guide
Quick start Tutorial
API Generated Documentation.
Must be searchable
Web Access
What else should it have? Also, based in your experience what is the best way to maintain (keep it up-to-date) and publish this type of documentation?
Keep your documentation in version control too.
Make sure on every page it has a version number so you know where your user has been reading from.
Get a CI server going and push documentation to a LIVE documentation site upon updates.
Do documentation reviews like you would code reviews.
Dog-food it :)
Kindness,
Dan