Skip to main content

Home/ HealthcareMetadata/ Group items tagged environments

Rss Feed Group items tagged

Malcolm McRoberts

Setting Up Test Controllers in Lab Environments - 0 views

  • This topic describes how to install and configure a test controller, and how to configure test agents so that you can run tests in a lab environment using Microsoft Test Manager.
Malcolm McRoberts

Security and Authentication - MongoDB - 0 views

  • MongoDB includes a basic authentication scheme that works with single server deployments and replica sets. However, the built-in authentication does not work with sharding, so for this and other cases, we recommend running the database in a secure environment.
  • The current version of Mongo supports only very basic security.  One authenticates a username and password in the context of a particular database.  Once authenticated, a normal user has full read and write access to the database in question while a read only user only has read access.
Malcolm McRoberts

MongoDB, BI and non-Relational Databases | SmartData Collective - 0 views

  • When considering implementing Operational BI solutions, many implementers first think of copying the operational data to an operational data store (ODS), data warehouse or data mart and analysing it there.  They are immediately faced with the problem of how to update the informational environment fast enough to satisfy the timeliness requirement of the users.  As that approaches real-time, traditional ETL tools begin to struggle.  Furthermore, in the case of the data warehouse, the question arises of the level of consistency among these real-time updates and between the updates and the existing content.  The way MongoDB is used points immediately to an alternative, viable approach--go directly against the operational data.
  • In the case of Operational BI, however, most experience indicates that the queries are usually relatively simple, and closely related to the primary access paths used operationally for the data concerned.
Malcolm McRoberts

Metadata registry - Wikipedia, the free encyclopedia - 0 views

  • Common characteristics of a metadata registry A metadata registry typically has the following characteristics: Protected environment where only authorized individuals may make changes Stores data elements that include both semantics and representations Semantic areas of a metadata registry contain the meaning of a data element with precise definitions Representational areas of a metadata registry define how the data is represented in a specific format, such as in a database or a structured file format (e.g., XML)
  • ISO 11179
  • A metadata registry is a central location in an organization where metadata definitions are stored and maintained in a controlled method.
  • ...2 more annotations...
  • Metadata registries are used whenever data must be used consistently within an organization or group of organizations
  • Organizations that need consistent definitions of data across time, between databases, between organizations or between processes, for example when an organization builds a data warehouse
Malcolm McRoberts

Data mart - Wikipedia, the free encyclopedia - 0 views

  • A data mart is the access layer of the data warehouse environment that is used to get data out to the users. The data mart is a subset of the data warehouse that is usually oriented to a specific business line or team. Data marts are small slices of the data warehouse
Malcolm McRoberts

Improving the User Experience of Automated Integration Testing - NYTimes.com - NYTimes.com - 0 views

  • We can collect the data when we run tests through Hudson, but that doesn’t make the output much more readable, doesn’t capture metadata (such as which environment configuration the tests ran against) and doesn’t even give useful historic snapshot data, as the jobs run different suites of tests based on parameters.
Malcolm McRoberts

Running Automated Tests from the Command Line - 0 views

  • You can use the MSTest.exe program to run automated tests in a test assembly from a command line. You can also view the test results from these test runs, save the results to disk, and save your results to Team Foundation Server.You can also use tcm.exe to run test cases with associated automation from the command line using a test environment.
Malcolm McRoberts

Running automated tests from the command line - 0 views

  • Visual Studio 2012 includes the following command-line tools for testing purposes: VSTest.Console.exe You can use the VSTest.Console.exe program to run automated unit and coded UI tests from a command line. VSTest.Console.exe is optimized for performance and is used in place of MSTest.exe in Visual Studio 2012. MSTest.exe You can use the MSTest.exe program to run automated tests in a test assembly from a command line. MSTest is used for load tests and for compatibility with Visual Studio 2010 test projects. MSTest can also be used to view the test results from these test runs, save the results to disk, and save your results to Team Foundation Server. TCM.exe Tcm.exe is a command-line utility that lets you perform the following tasks: Import automated tests into a test plan Run tests that are part of a test plan from the command line View a list of test items and their corresponding IDs to use when you import tests or run tests You can also use tcm.exe to run test cases with associated automation from the command line using a test environment.
1 - 8 of 8
Showing 20 items per page