In honor of Father’s Day this year, Saturday, June 19th, Sauce Labs is running a four-week long Twitter contest. Post now for your chance to win a free 12-month subscription to the awesome Dollar Shave Club – for you, or as a gift to Dad (or the little — or big — shaver of your choice!)
Why Dollar Shave Club? Using Sauce Labs, the company reduced its testing time from six hours to less than 10 minutes – saving more than 30 hours a week overall. That is some serious time shaved off! Check out the case study for details, and then help us celebrate both testing and dear old dad.
#TestDaddy Contest Rules
Participating is easy: tell us how Sauce Labs helps you save time, or “shave” time, off your busy day via a tweet to @saucelabs, using the hash tag #TestDaddy. Keep your response to 140 characters or less – no long, shaggy dog stories!
The contest runs now through Wednesday, June 15th. On Friday, June 17th, three winners will be announced via Twitter. Winners will be selected based on the creativity of their responses, and will win a free 12-month membership to the Dollar Shave Club.
So tell us how you’ve shaved time off your software development and testing process by using Sauce, and get in the running for a free subscription to Dollar Shave Club. Don’t forget to use the required hash tag, #TestDaddy to be considered, and hey, if you want to follow @saucelabs, Bob’s your uncle!
The contest is open to dads, moms, kids and distant relatives – and anyone using Sauce Labs, of course!
After several years of this ritual - one curious kid, unable to control his thought about why they get a chocolate everyday in the morning (note - prayer is long forgotten), asked his friend. "None knows why, my elder brother tells me that there used be some prayer before they got their chocolate" said the friend not so interested in the question.
Now, imagine this is a multi year social experiment conducted by school authorities in collaboration with educationists - what would you infer ? You might say, initially kids got their prize after prayer (a good and recommended activity to start the day in school) and when chocolate was given prior to any prayer, kids simply forgot or dropped the idea of prayer. Economists would call this as "incentive" to elicit a specific behavior from a group of people.
Let us come to our world and let us try to map prayer and chocolate to BDD (behavior driven development) and automation. As original proponents of BDD wanted it solve certain problems and automation apparently came out as chocolate, prize that follows doing BDD.
As I understand - BDD was intended to bring business analysts into the party, develop a common vocabulary between Dev, BA, Testing and stakeholders and address some of the perceived problems close cousin of BDD - the TDD, test driven development. Dan North explains the background and history of how he landed with the idea of BDD. As Dan narrates - the practice of BDD proposes to focus on the behavior (change from keyword "Test"or "requirement") software should demonstrate for a feature that client wants. In order to develop a common vocabulary - BDD needed to restrict the representation of this behavior using a set of keywords and the behavior required to be in a non technical language (remember they needed to bring BA's that are non technical into the party). Thus using a class of languages (meta language, I guess) like Gherkin which is a type of DSL (domain specific language) BDD ushered a practice where intended software behavior and corresponding scenario or an example was represented in a format like the one below
I want to [A feature or behavior]
So that [business outcome that is worth paying for]
Given [Initial or Preconditions]
When [ Action performed to invoke the feature]
Then [Expected result that software needs to demonstrate]
As Liz Keogh, one of early collaborators with Dan on BDD development, says -key challenge BDD was intended (broadly among other things) to solve is facilitate and improve communication, discussion and debates about what the behavior should be,among developers, testers, business analysts and stakeholders.
That was a prayer - BDD's objective for effective communication.
After looking format of BDD scenario/user story, full of keywords - a smart developer would have thought "I can parse this and generate a skeleton code which can be implemented later as automated test". This is that chocolate that was promised to everyone in the team. Thus a strong distraction for original objective of BDD was born in the form of automated tests out of BDD story/scenario.
The theme of automation attached to BDD become so powerful with loads of frameworks such as jBehave, Cucumber and others overshadowed everything related BDD. At some point of time, doing BDD meant using jBehave or cuccumber and creating automated tests.
The power distraction of automation (chocolate from our story) instantly hijacked communication/discussion about behavior (prayer) and practitioners BDD started doing only automation. This is the anti pattern that I wanted to highlight in this post. I have seen several instances where testers/developers/BA's were worried only about which tool or framework to use for BDD and which automation framework/library to use. The stakeholders on their part were sold on the idea that they would get "Executable specifications that come with dual benefit - representation of behavior and automated test". They could not ask more.
Alas, in the process, BA's, testers and developers instead of sitting together and discussing about what "Given" should lead to what "Then" or what "When" leads to what "Then's" - sat in silos and happily created loads of BDD stories and some tester or developer jumped straight away to implement automation.
I am not complaining about automation that is embedded in BDD per se - I would like people to reinstate the prayer - the focus on cross function collaboration, you can have your chocolate (automation) anyway.
Time to read Dan's post on introduction to BDD and also posts from Liz on the aspect of communication ?
You can now scale your load testing for video streaming with Hewlett Packard Enterprise LoadRunner. (Available beginning with version 12.53) Keep reading to find out how to utilize these capabilities.
Is your test environment secure? Do you know who has access to your test data, your source code, your design specifications?
There was a time, back in the days of stand-alone test systems and networks that were strictly local-area, when those questions would have been easy to answer. A co-worker or two might have been looking over your shoulder, but that would have been about it.
These days, however, applications are exposed to the public web, and such questions can have serious implications for your software’s security and your company’s bottom line. Software and IT companies may still have physical locations, but much of the development and testing is done off-site, by employees, contractors, and services that transfer data over the Internet, such as cloud-based testing solutions. That is why picking one who cares about your application security is important. Lets look at the risks, then at what a good solution looks like.
Most companies are reasonably security-conscious when it comes to software development, but does that security consciousness extend to your testing process and suite? For many companies, using an Internet-based testing service just makes good sense from both a practical and economic point of view. But when your QA department shifts its testing from in-house to online, do QA management and staff also shift their understanding of security from “stand-alone machines safe behind four walls” to “somewhere out there on the Internet”?What’s at Stake
Consider what can be at stake if outside parties gain access to your test data or your test environment:IP Theft
Unfortunately, not everybody in business sticks to the rules of fair play—and that includes the technology sector. Intellectual property is a valuable commodity, and for many technology providers, it is their main asset. This is particularly true for smaller companies and startups, which may not have had time to develop other assets, such as name-recognition or a reputation for high-quality products or services. IP is not hard to steal, since it generally consists of information that can be easily copied, compressed, encrypted, and transported. Often enough, sufficiently detailed (or even general) knowledge of an idea is sufficient for it to be stolen. If you are testing a feature or technology that is worth stealing, and if there is a way for IP thieves to gain access to your test environment, there is a reasonably good chance that they will break in. When that happens, you may find yourself not only competing with knockoffs of your software-in-progress, but also fighting in court to regain control of your proprietary technology and data.Competitors
If you’re doing anything worthwhile or potentially money-making, you have competition—and if your competitors are smart (which they almost certainly are), they’re watching you. They may play a cleaner game than IP thieves, but they want to know what you’re planning, what new technologies and services you’re in the process of implementing, how far along you are in developing them, and how well they’re working. Needless to say, if they know what mistakes you’re making, they can learn from them as quickly as you can. If your online test environment is not secure, it’s possible that your competitors have access to your test results, and may even be able to observe your tests while they are in progress. A test suite can give a sense of code, functionality, and potential issues and weak spots in your application. They’ll know what new features and technologies will be in your next release, and they’ll have a head-start on adding competing versions to their own products. If they can learn enough from watching you, they may even beat you to the market.Just Plain Privacy
Maybe you’re not testing anything that can be easily cloned by competitors or stolen. Maybe you’re working on things such as better implementations of known technology, and a new user interface that incorporates your brand-new, still-under-wraps company logo. There still may be some major security issues to keep in mind when it comes to online testing.
Consider this all-too-familiar scenario: Hackers break into a site, dig out some attention-getting information, and spread it all over the Internet. Very often, it turns out that what was mildly entertaining to the hackers is embarrassing or even damaging to the people and organizations affected by the leak. Do you want your upcoming feature list to become public knowledge while those features are still in the early development phase? Do you want your raw test data posted for anybody to see? Do you want your pre-release bugs to become just another occasion for lulz? Just one little break-in, into a non-secure test environment, could do all of that.Looking for Security
How do you find a secure online test environment? What are the key elements of online test security?
Besides such basics as a secure test infrastructure and physical on-site security, a truly secure online test service (such as Sauce Labs) should provide a suite of strong test-oriented security features:
- Dedicated, One-Time Virtual Machines. Each test VM should be spun up, used only for a single test, and then destroyed. VMs should not be recycled for multiple users, or even for multiple tests by the same user.
- Secure Communication. Client communication with the test system should be by secure VPN or tunneling. Client test scripts and data should only be cached temporarily on the test-system side, and never stored. Only the current test VM should be allowed to communicate with the client.
- No External Communication. All inbound channels of communication with the test VM other than client VPN/tunneling access should be disabled.
- No On-Site Storage of Test Data or Artifacts. Test data and other artifacts should never be stored at the test site. They should only exist in RAM on the test server, and should be sent to the client via secure connection. If they are stored as part of the test service, such storage should be in a secure cloud-based location, it should be for a limited time, and it should only be at the client’s discretion.
If an online service does not offer security features such as these, you cannot count on it to provide you with a secure testing environment. A genuinely secure software testing service, on the other hand, can guarantee that all of your test data will truly be for your eyes only.
Michael Churchman started as a scriptwriter, editor, and producer during the anything-goes early years of the game industry. He spent much of the ‘90s in the high-pressure bundled software industry, where the move from waterfall to faster release was well under way, and near-continuous release cycles and automated deployment were already de facto standards. During that time he developed a semi-automated system for managing localization in over fifteen languages. For the past ten years, he has been involved in the analysis of software development processes and related engineering management issues.
The team is proud to announce the release of 5.5, which features simplified concepts for easier triage and management of issues:
- New SonarQube Quality Model
- New Measures project page
- Increased vertical scalability, performance, and stability
With 5.5 we’ve boiled quality down to its essentials to make it easier to understand and work with. Now there are Reliability Issues, Vulnerability Issues and Maintainability Issues. Or, in plainer talk: bugs, vulnerabilities, and code smells. By drawing bugs and vulnerabilities out of the mass of issues, any operational risks in your projects are highlighted for expedited handling.
We’ve also updated the default Quality Gate to match the importance of these newly isolated concepts:
Also new in this version is a project-level Measures interface, which replaces the old metric drilldown. Click a metric from the project home page and you land at the new per-file metric value listing:
The Tree view offers a compact, per-directory aggregation, and the Treemap gives the familiar, colorful overview:
The metric domain page also offers a listing of metrics and project-level values, with a graphical presentation:
The Compute Engine has been moved into a separate process, and the number of worker threads made configurable (SONARQUBE_HOME/conf/sonar.properties), so users will no longer have to deal with a sluggish interface when analysis reports are being processed, and the memory requirements for processing can be handled separately from those for the web application:
Time now to download the new version and try it out. But don’t forget to read the installation or upgrade guide first! Even if you’ve read it before, it may be worth taking another look at the upgrade guide; we changed it recently.
It is imperative for businesses to keep up with today’s fast paced, “always-on” digital economy. With this constant need for speed in the delivery of applications and services, many organizations are turning to Virtual Desktop Infrastructure (VDI) deployments for their employees and internal customers. Find out how HPE LoadRunner supports the Teradici PCoIP helps.
This week marks a huge milestone in AutoMapper-land, the beta release of the 5.0 work we’ve been doing over the last many, many months.
In the previous release, 4.2.1, I obsoleted much of the dynamic configuration API in favor of an explicit configuration step. That means you only get to use “Mapper.Initialize” or “new MapperConfiguration”. You can still use a static Mapper.Map call, or create a new Mapper object “new Mapper(configuration)”. The last 4.x release really paved the way to have a static and instance API that were lockstep with each other.
In previous versions of AutoMapper, you could call “Mapper.CreateMap” anywhere in your code. This made two things difficult: performance optimization and dependent configuration. You could get all sorts of weird bugs if you called the configuration in the “wrong” order.
But that’s gone. In AutoMapper 5.0, the configuration is broken into two steps:
- Gather configuration
- Apply configuration in the correct order
By applying the configuration in the correct order, we can ensure that there’s no order dependency in your configuration, we handle all of that for you. It seems silly in hindsight, but at this point the API inside of AutoMapper is strictly segregated between “DSL API”, “Configuration” and “Execution”. By separating all of these into individual steps, we were able to do something rather interesting.
With AutoMapper 5.0, we are able to build execution plans based on type map configuration to explicitly map based on exactly your configuration. In previous versions, we would have to re-assess decisions every single time we mapped, resulting in huge performance hits. Things like “do you have a condition configured” and so on.
A strict separation meant we could overhaul the entire execution engine, so that each map is a precisely built expression tree only containing the mapping logic you’ve configured. The end result is a 10X performance boost in speed, but without sacrificing all of the runtime exception logic that makes AutoMapper so useful.
One problem with raw expression trees is that if there’s an exception, you’re left with no stack trace. When we built up our execution plan in an expression tree, we made sure to keep those good parts of capturing context when there’s a problem so that you know exactly which property in exactly which point in the mapping had a problem.
Along with the performance issues, we tightened up quite a bit of the API, making configuration consistent throughout. Additionally, a couple of added benefits moving to expressions:
- ITypeConverter and IValueResolver are both generic, making it very straightforward to build custom resolvers
- Supporting open generic type converters with one or two parameters
Overall, it’s been a release full of things I’ve wanted to tackle for years but never quite got the design right. Special thanks to TylerCarlson1 and lbargaoanu, both of whom passed the 100 commit mark to AutoMapper.
Post Footer automatically generated by Add Post Footer Plugin for wordpress.
While the term “wire data” may be relatively new, the concept isn’t; probes and capture agents have been collecting and examining network traffic almost from the beginning of network time. The term has been used casually by many network analysts, is particularly popular with Wireshark users, and – in a very casual Google search – […]
Why should we choose TestRail? This is a question we routinely receive from customers who are just about to start their trial of our modern test management tool. It’s a fair question to ask! There are many test management tools available, and why should TestRail be the best fit for their need? Fortunately, in many cases once teams try TestRail and experience its fast and modern user interface, as well as TestRail’s many unique features that help teams work faster and more efficiently, teams quickly understand the advantages TestRail brings to the table. In this article we are going to highlight some of TestRail’s unique productivity features that will help your team save many many hours every week compared to other test management tools.
The number #1 reason teams switch to TestRail is the significant increase in productivity teams get by adopting TestRail, as well as the resulting time, resource and cost savings. We receive this feedback from users all the time and teams often tell us that they spend a lot of time in a test management tool every day, so TestRail makes a huge difference for them. Many teams migrate to TestRail every week from all kinds of tools. This includes legacy ALM systems, JIRA add-ons and all kinds of open source and commercial test management tools.
Does tool productivity really matter? If you value the time and resources (and related costs) of your testing team, productivity and efficiency should be your number one priority when selecting a test management tool. Engineers, developers and testers cost huge amounts of money every month, so you want to make sure you give them the best tools available to get the job done.
If you consider TestRail’s many productivity features combined with unique capabilities such as its deep JIRA/issue and test automation integration, rich reporting & metrics, important enterprise and customization options and much more, as well as very competitive pricing, it’s easy to see why many teams adopt TestRail. Make sure to review the below feature highlights when comparing TestRail with other tools, it will have a big effect on your team!Table of Contents
- 1. Three-Pane FastTrack Interface
- 2. Integrated Keyboard Shortcuts
- 3. Drag & Drop plus Screenshot Support
- 4. Test Report & Metrics Automation
- 5. JIRA & Issue Tracker Defect Push
- 6. Test Plans & Platform Configurations
- 7. Bulk Editing Cases & Adding Results
- Is TestRail Right For Your Team?
TestRail’s three-pane FastTrack view allows you to see your section list, list of test cases and the details of the selected test side by side. This view is incredibly productive as it allows you to quickly open a test, review the test steps, add a result and jump to the next test. All this without navigating to another page, switching contexts or moving to another section. The three-pane view is fully integrated into TestRail and is available from any test run or suite page. Simply select a test case via the arrow icon to expand the view and see all test details at a glance.
The view also integrates all features known from the test and case pages, so you can easily add results, comments and review related details. And best of all: with TestRail’s new responsive layout improvements, and separately configurable columns, you can also use and benefit from TestRail FastTrack if you have a smaller display.TestRail FastTrack: incredibly productive three-pane view for faster testing
With TestRail 4.2 we also added integrated keyboard shortcuts for often used features so you can more easily save test cases & forms, add new test steps, jump to the next test or add test results. TestRail supports shortcuts you are most likely already familiar with from other applications, so you can save your test case changes via Ctrl+s, edit most entities by pressing e or navigate between tests via j and k. Please refer to our our detailed overview of key shortcuts we support in TestRail.
For TestRail’s unique FastTrack interface we also introduced another related productivity feature: we now support a single key press shortcut to mark a test as passed and directly select and load the next test as part of TestRail FastTrack. To support this, we added new Pass & Next actions, along with additional quick action buttons for other test results. Likewise, we added various additional keyboard shortcuts to make it even faster to navigate between test cases, open the Add Test Result dialog, toggle the three-pane view and add comments.
Add test results & jump to the next test with a single mouse click or key press
With TestRail 5.2 we also added full support for drag & drop to make it very fast to add files and images to your test case, text fields and test results. To drag images, screenshots or any other file to TestRail, simply drag the file from another application or Windows Explorer/Mac Finder to TestRail. Depending on the page you are on, TestRail will automatically show all valid and available drop targets, so it’s easy to attach all kinds of files to test cases, or directly embed images in any Markdown enabled text field.
Full drag & drop support for files and images with full screenshot integration
But we didn’t just want to make it easier to add images and attachments via drag & drop. Modern web browsers such as Google Chrome and Microsoft Edge are slowly adding better support for copy & pasting images. So TestRail 5.2 introduced the first web-based test management support to make it much easier to paste images into TestRail’s Markdown-enabled text fields, as well as the Add Image dialog (Google Chrome for now). For example, simply select any text field in TestRail, such as the steps field or test result comment, and paste an image. TestRail will then automatically upload the image and add the related inline Markdown code to display the pasted image in the field.
Fast adding of images and screenshots via copy & paste to any of TestRail’s text fields
Adding more useful built-in reports that help our customers answer important questions about their testing efforts and help teams make informed decisions during development was a major design goal of TestRail 3.0. Making it as easy and flexible as possible to run, schedule and share said reports is equally important, so we added a bunch of useful options for this. TestRail allows you to generate new reports on a pre-defined schedule so you can, for example, automatically generate new reports once a day or once a week so your team or project stakeholders get fresh reports automatically.
Schedule and automatically generate & forward reports on autopilot
TestRail also makes it extremely easy to share reports with both TestRail users as well as external stakeholders such as customers. Besides hosting and displaying reports inside TestRail, you can also forward reports as HTML attachments via email or download reports to archive them. Combined with the above mentioned scheduling feature you can keep your entire company updated on your latest testing efforts automatically and run your reporting on autopilot, awesome!
TestRail’s deep JIRA and other issue/defect tracker integration makes it super productive to link test cases to requirements and user stories, link test results to defects and bug reports, directly look up details of linked issues and run detailed coverage reports. One of the most useful features of our integration is that you can directly push bug reports from TestRail to JIRA and a dozen of other tools. Has one of your testers found an issue during testing? Easy! Simply push a bug report to your team’s issue tracker with just 1 click.
Directly push bug reports & defects from test results to JIRA and a dozen other tools
But the integration doesn’t stop here: TestRail automatically remembers all relevant settings such as the issue tracker project, issue type, component, bug priority and other attributes of your issues on a per-project basis. So when a tester pushes another bug report from the same project, all settings are automatically restored for even faster bug creation. With TestRail’s deep JIRA and issue tracker integration there’s no need to synchronize any bug reports or store bug reports in multiple places: TestRail always directly integrates with your existing tools.
A very typical use case for many testing teams is the requirement to run their tests against different platforms and configurations. This can include different web browsers, operating systems, mobile devices, specific hardware platforms or a combination of any of these. Many testing tools make such tests very time consuming or even impossible to run. Not so with TestRail’s extensive test plan and configuration features! Test plans make it super easy to run your tests against all kinds of configurations and platforms with just a few clicks: check out the video.
Create extensive test plans with automatic test run creation for configurations
You only need to configure your project configurations once and can easily reuse all configurations across test plans. TestRail automatically creates new test runs for each selected configuration combination. Want to create separate runs for all your supported web browser, operation systems, mobile devices, all relevant combination and assign them to different testers? It just takes a few clicks with test plans & configurations! Test plans & configurations help you and your team save many hours with planning, running and reporting your software tests.
TestRail also includes powerful options to bulk edit your test cases to update any of the case attributes with a single click. Whether you want to change the preconditions of all test cases in a section, update the type of your cases in an entire suite or carefully filter and change the priority of thousands of cases at once: the bulk-edit feature makes this super easy.
Bulk edit test cases and add test results to many tests at once with a single click
You can either select the test cases you want to update manually, or you can use the bulk-edit feature together with our powerful filtering options. But bulk operations are not just limited to editing cases. You can also move, copy and delete many test cases at once so you can better organize and refactor larger projects. You can also easily add results to many tests in a run and assign many tests or entire sections to different testers with a few clicks, saving you a lot of time when planning, assigning and running your tests.
Many thousand companies are using TestRail to supercharge their software testing, including many of the world’s largest and most successful organizations. And many new teams are starting to use TestRail every week. Should your team switch to and adopt TestRail as well?
A big reason so many teams of all sizes with all kinds of development methodologies switch to TestRail is that all teams have one thing in common: every team is looking for the one tool that helps them work as efficiently as possible. So the chances are very good that TestRail would be a great fit for your team as well, and you should at least give it a try with our free 30 day trial. It only takes a few minutes to get started!
Many life sciences organizations find it difficult to achieve compliance with the FDA’s 21 CFR Part 11 guidance on electronic records and electronic signatures. Their stumbling point is often version control for source code and other digital assets, because the tools they use don’t support electronic signature and audit capabilities. Surround SCM, however, has these capabilities built in.
Surround SCM includes complete electronic version control, with the ability to capture electronic signatures at key points within a controlled process. With Surround SCM’s configurable workflow and versioning, you have complete assurance you are working with the correct version of source code, SAS data sets, text-based files, and many other digital assets that may not be managed or controlled well in other solutions.Enhance Your QMS with Additional Control and Versioning
By itself, a traditional quality management system (QMS) can cause business interruptions; it doesn’t integrate with the other tools you use and it doesn’t fit the daily process you follow.
Surround SCM doesn’t replace your QMS, but complements it by providing additional control and versioning for complex assets that require parallel development and tight security. Because Surround SCM is a source code management tool first, it has all the capabilities you would expect to manage assets:
- Check in/out
- Code reviews
What’s more, Surround SCM integrates with the tools you use the most throughout your development process.Improve Data Analysis, Reporting, and Change Management
Going beyond traditional source code management tools, Surround SCM can be configured to keep non-software developers, such as analysts and statisticians, working in the tools they’re familiar with. They’ll be happy, because they won’t have to learn yet another tool with audit reporting and electronic signature assurance.
Because Surround SCM manages large text-based and binary files in a relational database, you’ll experience better data analysis and reporting. And if you’re a TestTrack user, you get the added benefit of having these controlled assets automatically included in a traceability matrix report. The visibility of the associated work item is increased, as well, which allows for better change management.Strengthen Data Security and More
Surround SCM also gives you more security controls and other features that allow you to:
- Limit access to authorized users
- Protect IP with encrypted security
- Record timestamps for each and every change
- Streamline and automate core processes with configurable workflow
- Authenticate core approvals with electronic signatures
- Report and validate electronic records for auditing
All of these powerful controls and features are combined in Surround SCM to give you improved version control and better compliance with FDA 21 CFR Part 11.
Beginning with LoadRunner 12.53 load testing software, we added a usable and simple feature that enables the user to add REST API based syntax within WEB protocol scripts. We now support a web_rest function that submits a REST request.
Keep reading to find out how to use this capability.