Skip to content

Feed aggregator

NeoLoad 5.2 Announced

Software Testing Magazine - Tue, 05/03/2016 - 17:20
Neotys has announced NeoLoad 5.2, an enhanced version of its load and performance testing solution. The 5.2 release, currently available in Beta is all about making NeoLoad users faster. NeoLoad 5.2 is also the first load testing solution to support HTTP/2 applications. An extensive list of other enhancements, including new integrations and technologies support, make this release of NeoLoad particularly exciting for both new and existing users. NeoLoad 5.2 Key Enhancements User Path Update – Maintaining scripts as applications change is a major challenge for almost everyone. Saving testers massive amounts of time, NeoLoad 5.2 provides the ability to quickly update designed user paths (formerly called VU profiles) with a new recording while automatically keeping variable extractors, think times, SLAs, loops, javascript, validations and more from the original user path design. Support for HTTP/2 Applications – HTTP/2, the network protocol that is being called “the future of the internet”, is here, and NeoLoad 5.2 is the first load testing tool on the market to support it. C# Client for Data Exchange API – NeoLoad already captures end user experience metrics under load from Java-based functional testing tools. Now, NeoLoad 5.2 supports C# tools for gathering end user experience metrics from browsers and devices. This enables integrations with tools like Selenium, Appium, Quamotion, Ranorex, Rapise or any tool with C# scripts.
Categories: Communities

JIRA is Just a Click Away with Our New Plugin

Sauce Labs - Tue, 05/03/2016 - 16:59

As more and more devs work in agile teams, they need tools to plan, track, and release software and many of them use JIRA. As a tracking tool, JIRA is amazing for collaboration and project planning. For many teams, JIRA is the place of record for everything in the software development lifecycle. We have found that many of our customers use JIRA and the #1 product ask was to integrate Sauce Labs’ test results with JIRA so it would be simple to track all the tests associated with a project in one place.

Let’s say you are running an automated or manual test on Sauce Labs and find a bug. You want to add it to JIRA so that someone on your team can take a look or so that it can be prioritized in the backlog. Historically, one would have to download all the Sauce assets, login to JIRA, create a ticket, and upload the assets again. This can be tedious when you’re running lots of tests.

With Sauce Labs for JIRA, this is all simplified and automated. With the click of a button you can now create a JIRA ticket directly from your Test Details page. The plugin gives you the option to upload the screenshots, logs, and video link to your tests, making it easy to share out among your team.

To download Sauce Labs for JIRA, visit the Atlassian Marketplace:  To read more, visit our JIRA integration Docs page.

Happy Testing!

The Sauce Labs Ecosystems & Integrations Team

Categories: Companies

Nordic Testing Days, Tallinn, Estonia, June 1-3 2016

Software Testing Magazine - Tue, 05/03/2016 - 15:00
The Nordic Testing Days is a three-day conference focused on software testing that target as an audience the professional software testers from the Northern European countries. The first day proposes tutorials and the two other days are full of short talks and workshops. The conference has all the important topics of testing and a wide cast of presenters. In the agenda of the Nordic Testing Days conference you can find topics like ” How to Be an Explorer of Software”, “Exploratory Testing Made Simple”, “Automated Acceptance Test by Developers and Automated Functional Testing by Testers”, ” Using Retrospectives for Better Quality Assurance”, “Extending Selenium Beyond Its Capabilities”, “Automated Accessibility Testing in the Continuous Integration Pipeline”, “Gamification in Software Testing”, “The Empowered Tester: How To Test & Release 32 Sites Daily and Keep Sane”, “A Day Of Lean Software Testing”, “Thinking And Working Visually for Software Testers”, “Improvising for Testers – What to Do When You Don’t Know What to Do Next”, “Advanced Test-Driven Development Scenarios: From Mocks to Legacy Code”, “Missing Bugs, Cognitive Bias and Mindsets”, “Mastering complexity: The art of automated testing”. Web site: Location for Nordic Testing Days conference: Sokos Hotel Viru, Viru Valjak 4, Tallinn, Estonia
Categories: Communities

What’s New in Surround SCM 2016 Documentation

The Seapine View - Tue, 05/03/2016 - 14:00

Have you upgraded to Surround SCM 2016 yet? If so, here’s a quick rundown of the documentation updates you might want to check out:

Note: New servercomplianceoption and mainlinecomplianceoption commands are also available to configure these options from the Surround SCM CLI.

Remember, you can always find documentation on our web site. If you have documentation suggestions, please let us know.

Categories: Companies

Software Testing and the Hacker Way

Testing TV - Tue, 05/03/2016 - 10:52
This video explains about how Facebook engineers test their software. Facebook doesn’t have QA department, but the new code is pushed to the site every day, while the backend infrastructure is continuously being developed. You will learn how hackers at Facebook test their code, services and entire infrastructure in a safe and controlled way to […]
Categories: Blogs

Master the Essentials of UI Test Automation Series: Chapter Seven

Telerik TestStudio - Tue, 05/03/2016 - 00:47
Final Chapter 7: Improving on Your Success As you move through (or finish!) your first project, you should be looking to get as much feedback as possible. Constant feedback and learning is vital to any organization. It's especially important when you're diving into a brand-new approach to delivering your software... 2015-04-08T20:14:34Z 2016-05-02T22:35:31Z Jim Holmes
Categories: Companies

One Second Services

Radyology - Ben Rady - Mon, 05/02/2016 - 22:25
Microservices have problems. Monoliths have problems. How do you wind up in a happy middle? Here's what I do. As I talked about in my new book, I'm skeptical of starting systems with a microservice architecture. Splitting a new system... Ben Rady
Categories: Blogs

Choose an APM Tool for the Solution – not for the Problem!

Just last week a senior Hybris consultant shared the story of a customer engagement on which he was working. This customer had problems, serious problems! We are talking about response times far beyond the most liberal acceptable standard! They were unable to solve the issue in their eCommerce platform – specifically Hybris. Although the eCommerce project was delivered by a System Integrator/Implementation […]

The post Choose an APM Tool for the Solution – not for the Problem! appeared first on about:performance.

Categories: Companies

Planning for Mobile Testing Challenges

Software Testing Magazine - Mon, 05/02/2016 - 15:28
When you develop applications, it is hard to ignore mobile devices. Testing mobile applications provides however some additional challenges than don’t exist for desktop or web applications. In this article, Kostyantyn Kharchenko explains some of the specific challenges that you should include in your mobile testing plans. Author: Kostyantyn Kharchenko, Svitla, It was already 4 years since Julia had started her career as a QA tester and she felt quite confident with any task. At one of the regular planning meetings, the company Product Owner announced that their application was going to have a mobile version as the market needed it. Julia was assigned to be in charge of all testing activities for this new version of the application and create a mobile testing strategy. The first thing that she was expected to do was to create a list of possible challenges and solutions for the next meeting to discuss and create a strategy for testing. This was a new experience for Julia but she understood that the time demands these changes and this was a great opportunity for her to acquire new skills and knowledge. The research started and Julia created the following report: Challenge #1. The Biggest Mobile Testing Challenge is Devices There are approximately thousands of different mobile devices through which our customer may want to access our mobile app. So, testing of our mobile application should take into account all these devices. Ignoring some of the devices equals to loosing numerous potential customers. Possible solutions: [...]
Categories: Communities

Just Released: TestTrack 2016

The Seapine View - Mon, 05/02/2016 - 13:00

new_releaseShare formatted data. Navigate key relationships.
Keep everyone informed.

TestTrack 2016 was just released! This version adds new features that make it even easier to analyze, view, and share traceability and progress information, including:

  • Export TestTrack items to Microsoft Word
  • View and navigate to linked items directly from list windows
  • Display note widgets on dashboards

To check out TestTrack 2016’s new features, visit

Don’t have TestTrack 2016 yet?

Upgrades are free if you have a current TestTrack support and maintenance plan. If you’re not already using TestTrack, try it out today.

Categories: Companies

Toujours Testing

Hiccupps - James Thomas - Mon, 05/02/2016 - 06:46

Some time ago, maybe even a year ago now, one of my team said that she had been watching me. I acted cool - although that may have been the onset of a cold sweat - but fortunately my dark secrets remain mine and her observation was simply that, to her mind, I am always testing. She gave a couple of examples:
  • When the test team were being given an expert-level product demo, I took notes not only on the functionality but also on the way that that information was being communicated to us, verbally and in slides, and I fed that back to the business because what we were watching was similar to the content of our customer demos.
  • When I set a piece of work - for myself or others - I will frequently have a secondary aim other than simply getting the piece of work done, and that aim often has an evaluation or assessment element to it.

And on reflection I think she's right. This is something that I have done, and do do. These days, I believe, I do it more explicitly than I used to because, over a long period of time and particularly by observing myself, I realised that this was my intuition and instinct, and I have found it personally valuable.

Right now at work we're considering some potentially significant changes to the way we organise ourselves and I'm spending time thinking about possibilities and exploring ramifications of them, mostly as thought experiment and by talking to members of the team. When I had the opportunity to try, in a small way, one of the possibilities, I took it. It's a possibility I instinctively shy away from and so I was very interested in my reaction to it. And later I  followed up with a recipient of my action too, to understand their feelings and explain why I did what I did.

I like to make myself and my work open for others to test and, when I do, the questions that follow mean that I learn things and, as a team, we do a better job overall. I am happy when someone on my team finds one of my mistakes and we correct it, although it took me some time to see and understand my feelings of defensiveness in those kinds of situations. (And they never go away.) Through this kind of self-testing I have arrived at knowledge about myself that I can codify and use to guide how I want to behave in future.

I also test myself by issuing challenges. Talking at EuroSTAR 2015 was the culmination of a 12-month challenge to try to get over increasing nervousness at public speaking. (I'll have more to say about that another time.)

I try hard to write reports in terms of testable assertions. And then, before delivery, I test them. I'll frequently find places where I've made too general or specific a claim, or I might feel that I need to go and look again at some data to check that I can back up what I'm saying. For instance, in an earlier draft of this post, the next paragraph started "So, yes, I am always testing ..." But it doesn't start that way any more because in proofing I asked myself "really, always testing? Always?"

So perhaps I can agree that I am always checking, challenging, exploring, investigating, ... Maybe that's why testing felt like a good fit when I stumbled into it. I like the spirit of the suggestion and - to the extent I'm prepared to commit to a literal "always" - I am always testing. Or, to tune it still further, I am always doing things that I think are consistent with and conducive to being a good and improving tester.

So I was particularly intrigued to read Harnessed Tester writing about wanting to switch testing off:
... how do you switch off the tester in you (if you do even manage it at all)? Are you able to function in the “Real World” without slipping into your profession or do you find yourself testing things you shouldn’t or don’t need to test? Do you even see it as a bad thing?I don't ever want this to be switched off.  I want to work it, to exercise it, to train it. I seek out opportunities to put it to use. I love this quote from George Carlin:
The brain is a goal-seeking and problem-solving machine, and if you put into it the parameters of what it is you need or want or expect, and you feed it, it will do a lot of work without you even noticing.I quoted it in Your Testing is a Joke where I described how I use humour as just such a training device, as a tool for feeding my brain.

I don't ever want this to be switched off. Since having children, I have become interested in how they see and interact with the world. I encourage my two daughters to have their enquiring mind turned on at all times and I praise them when they find a new perspective or ask a question or seek information. I am prepared (most times) to keep answering those long chains of why questions until they get bored, and I try find opportunities to provoke thoughts that will start their thinking process off.

I don't ever want this to be switched off. Last Christmas I bought my family a shared present of How to be an Explorer of the World and we've done several of the experiments together. Last month we went on an adventure walk in Ely.  My youngest daughter was particularly inspired by one task that I set: find something hidden. She's since begun to read Pippi Longstocking and styles herself a "Thing Searcher" and, while I was weeding the drive (and on the side listening to an interview with James Bach) last weekend, she interrupted me:
"Dad, how can I find things that no-one else finds?" she asked."You could look where no-one else looks" I replied.And so that's exactly what she did, initially by standing on a wheelie bin to inspect the top of the hedge.

I don't want this to ever be switched off. What I want is for asking, probing, looking, questioning, reviewing, being creative, and exploring to be second nature. I think that these are valuable skills in life, but also that if they become what you just do  then, as a tester, you can more often get on with a task and not spend explicit time on the techniques.

I don't ever want this to be switched off. However, where I think that Harnessed Tester has got a point, and it's a strong one, is that it's important to be able to deploy these skills appropriately, to make sensible use of them, to report your findings from it in a way that's acceptable and beneficial to you, to whoever you are dealing with and to the context you find yourself in.

And that, by Weinberg's definitions, is about acting congruently, (see e.g. Managing Teams Congruently) which is one of the challenges I have set for myself and have been working on for the last couple of years.

And I've told my team that I'm dong it.

And I know that they are watching...
Categories: Blogs

Validation inside or outside entities?

Jimmy Bogard - Fri, 04/29/2016 - 21:45

A common question I get asked, especially around a vertical slice architecture, is where does validation happen? If you’re doing DDD, you might want to put validation inside your entities. But personally, I’ve found that validation as part of an entity’s responsibility is just not a great fit.

Typically, an entity validating itself will do so with validation/data annotations on itself. Suppose we have a Customer and its First/Last names are “required”:

public class Customer
    public string FirstName { get; set; }
    public string LastName { get; set; }

The issue with this approach is twofold:

  • You’re mutating state before validation, so your entity is allowed to be in an invalid state.
  • There is no context of what the user was trying to do

So while you can surface these validation errors (typically from an ORM) to the end user, it’s not easy to line up the original intent with the implementation details of state. Generally I avoid this approach.

But if you’re all up in DDD, you might want to introduce some methods to wrap around mutating state:

public class Customer
  public string FirstName { get; private set; }
  public string LastName { get; private set; }
  public void ChangeName(string firstName, string lastName) {
    if (firstName == null)
      throw new ArgumentNullException(nameof(firstName));
    if (lastName == null)
      throw new ArgumentNullException(nameof(lastName));
    FirstName = firstName;
    LastName = lastName;

Slightly better, but only slightly, because the only way I can surface “validation errors” are through exceptions. So you don’t do exceptions, you use some sort of command result:

public class Customer
  public string FirstName { get; private set; }
  public string LastName { get; private set; }
  public CommandResult ChangeName(ChangeNameCommand command) {
    if (command.FirstName == null)
      return CommandResult.Fail("First name cannot be empty.");
    if (lastName == null)
      return CommandResult.Fail("Last name cannot be empty.");
    FirstName = command.FirstName;
    LastName = command.LastName;
    return CommandResult.Success;

Again, this is annoying to surface to the end user because I have one validation error at a time being returned. I can batch them up, but how do I correlate back to the field name on the screen? I really can’t. Ultimately, entities are lousy at command validation. Validation frameworks, however, are great.

Command validation

Instead of relying on an entity/aggregate to perform command validation, I entrust it solely with invariants. Invariants are all about making sure I can transition from one state to the next wholly and completely, not partially. It’s not actually about validating a request, but performing a state transition.

With this in mind, my validation centers around commands and actions, not entities. I could do something like this instead:

public class ChangeNameCommand {
  public string FirstName { get; set; }
  public string LastName { get; set; }

public class Customer
  public string FirstName { get; private set; }
  public string LastName { get; private set; }
  public void ChangeName(ChangeNameCommand command) {
    FirstName = command.FirstName;
    LastName = command.LastName;

My validation attributes are on the command itself, and only when the command is valid do I pass it to my entities for state transition. Inside my entity, I’m responsible for successfully accepting a ChangeNameCommand and performing the state transition, ensuring my invariants are satisfied. In many projects, I wind up using FluentValidation instead:

public class ChangeNameCommand {
  public string FirstName { get; set; }
  public string LastName { get; set; }

public class ChangeNameValidator : AbstractValidator<ChangeNameCommand> {
  public ChangeNameValidator() {
    RuleFor(m => m.FirstName).NotNull().Length(3, 50);
    RuleFor(m => m.LastName).NotNull().Length(3, 50);

public class Customer
  public string FirstName { get; private set; }
  public string LastName { get; private set; }
  public void ChangeName(ChangeNameCommand command) {
    FirstName = command.FirstName;
    LastName = command.LastName;

The key difference here is that I’m validating a command, not an entity. And since entities themselves are not validation libraries, it’s much, much cleaner to validate at the command level. Because the command is the form I’m presenting to the user, any validation errors are easily correlated to the UI since the command was used to build the form in the first place.

Validate commands, not entities, and perform the validation at the edges.

Post Footer automatically generated by Add Post Footer Plugin for wordpress.

Categories: Blogs

TestTrack 2016 Sneak Peek: Recording and Slides Now Available

The Seapine View - Fri, 04/29/2016 - 12:52

webinarIn this sneak peek of TestTrack 2016, Gordon Alexander, Seapine Solutions Consultant, provided a preview of the key new features including how to:

  • Export Items to Word. You can now export all TestTrack items to Word! The completely rewritten export functionality makes it easy to produce documents that include the exact data you need, in the exact Word format you want.
  • View and Navigate to Linked Items. To quickly see links between items, you can now add columns with linked item information to list windows. Want to see more? Click a linked item and go straight to it to see more details.
  • Use Note Widgets with Dashboards. Want to easily share getting started information with new team members, provide links to important information for a sprint, or provide team contact information? Put a note, which can be seen by everyone, right on a dashboard.

And here’s a link to the slides used in the presentation:

Categories: Companies

Sauce Labs Named a Contender Among Mobile Test Automation Tools

Sauce Labs - Thu, 04/28/2016 - 22:05

We are happy to announce a new industry citation for Sauce Labs: our inclusion in “The Forrester Wave™: Mobile Front-End Test Automation Tools, Q2, 2016.” The Wave is an influential report by leading research firm Forrester Research, and Sauce Labs was one of 10 companies selected for inclusion.

This Wave is based on an evaluation of 40 criteria across 10 vendors that considers how each provider measures up to help application development and delivery. Sauce Labs was among vendors cited as a “Contender” in the report. On describing Sauce, the report states:

Sauce Labs is the open source champion, offering comprehensive target app types … Sauce Labs successfully embraces the bring-your-own-tools (BYOT) and pick-your-favorite-language approaches to mobile app testing, which should make most developers happy. Focusing on automation and CI, it offers a robust, cloud-only testing solution that includes virtual machines for testing web and mobile applications as well as real devices. It satisfies security-conscious environments through a secure connection back into the data center using Sauce Connect.

More than anything, we are beyond excited that our Real Device Cloud (RDC) was included in such a significant report. Especially as we know Forrester went through an exhaustive evaluation of Sauce Labs that looked at factors including product fit, customer success, and Forrester client demand.

We believe this report provides Sauce Labs with huge visibility to potential new users, as many North America Fortune 1000 companies are Forrester clients. We are excited to be a part of the growing Mobile testing market, we are encouraged by the recognition of our strategy and roadmap, and we are thrilled with the momentum the Sauce Labs Real Device Cloud has gained in a short amount of time.

Want to learn more about automated mobile testing? Download our free report, “Automated Mobile Testing Requires Both Real Devices and Emulators“. 

Categories: Companies

Your Testing is a Joke

Hiccupps - James Thomas - Thu, 04/28/2016 - 22:00

My second eBook has just been released! It's called Your Testing is a Joke and it's a slight edit of the piece that won the Best Paper prize at EuroSTAR 2015. Here's the blurb:
Edward de Bono, in his Lateral Thinking books, makes a strong connection between humour and creativity. Creativity is key to testing, but jokes? Well, the punchline for a joke could be a violation of some expectation, the exposure of some ambiguity, an observation that no one else has made, or just making a surprising connection. Jokes can make you think and then laugh. But they don't always work. Does that sound familiar? This eBook takes a genuine joke-making process and deconstructs it to make comparisons between aspects of joking and concepts from testing such as the difference between a fault and a failure, oracles, heuristics, factoring, modelling testing as the exploration of a space of possibilities, stopping strategies, bug advocacy and the possibility that a bug, today, in this context might not be one tomorrow or in another.  It goes on to wonder about the generality of the observations and what the value of them might be before suggesting ways in which joking can provide useful practice for testing skills.  There are some jokes in the eBook, of course. And also an explanation of why any groaning they provoke is a good sign… And in case you're wondering, my first eBook was called My Software Under Test and Other Animals. It's got some groanworthy moments too.
Categories: Blogs

Why is Manual QA Still So Prevalent?

Sauce Labs - Thu, 04/28/2016 - 17:00

This past week I casually heard comments alluding to the imminent death of the QA Analyst or Manual Tester. (To be clear, I am not referring to the QA Automation Engineer, who builds test automation.)

Not only does the function not seem to be going away, recruiters are still out their hunting testers down. Out of curiosity I did my own review of randomly selected job posts from Monster and Indeed for average QA positions, and discovered that there are still a lot of jobs available for manual testers.

With the importance of catching bugs early, and the ability to automate all testing, why do companies and projects resist the investment in CI and test automation? I will explore the reasons why now, and whether the resistance is good or bad.

Legacy Products

Let’s face it. There is a whole generation of legacy products, supported by legacy teams. In my recent review of job openings for manual testers, the listings tended to be for companies that have been around for a long time, are large, and have mature product lines. In the DC area, the job openings tended to be tied to government contracts. Surprisingly, the number of jobs in San Francisco that didn’t require automation skills was almost identical. Again, those companies tended to be more mature, with processes in place that work for them.

Management Buy-in

In order to drive a development team to embrace automation, it requires upper management’s support and direction. I’m not just talking about QA management, but the development organization as a whole. How many times have you heard a QA manager say the team is going to be handling automation, only to see the efforts fail due to lack of buy-in from other organizations?

Why don’t they embrace automation practices? Switching to an automation-first approach costs time and resources. Project timelines will take a major hit as teams shift gears. If QA is expected to automate without product buy-in on reduced capacity, without developer support to assist with technical details, and without DevOps to help with infrastructure, the effort will be daunting, to say the least.

Development Team Buy-in

Even after all responsible management has signed off and provided direction to scrum teams to start embracing automation, there is still an established mindset that needs to be overcome. I’ve often heard “its QA’s job to test.” When QA is coming up to speed on automation practices, they need help from the scrum team to pick up the testing slack.

Why don’t they embrace automation practices? The scrum team is not taking a “team owns QA” approach. They still think QA is there to catch all of their issues. If a team took ownership of QA, they could pick up a lot of manual efforts, including strategy and exploratory testing via team Bug Bashes.

The QA Automation Engineer can help smooth the transition with developers by working closely with them to:

  • Establish best practices, such as those for UI element locators
  • Telling them what they need, such as mock data
  • Doing more upfront work, such as creating the Gherkin code for Behavior Driven Development (BDD) for the stories for the sprint.
QA Analyst Buy-in

QA Analysts come from many different backgrounds. While a lot of QA talent is hired out of college with software related degrees (and they’re hired as QA Automation Engineers), there are still many in the manual world. I personally love to hire from our support teams, as they are product experts and customer-focused.

Why don’t they embrace automation practices? Learning to automate takes effort. Besides the blocks noted above, the analysts themselves have hurdles to overcome:

  • Time – If the company is not behind the effort, it is up to the analyst to learn on his or her own time. While there are plenty of free online lessons available, it takes a major time investment.
  • Motivation – How many times have you taken courses to help you learn automation but never get to apply the knowledge? Unless someone is looking for another job, there may be no motivation to make the effort if the previously mentioned blocks exist.
  • Don’t know where to begin – There is so much out there. The hardest thing is knowing which tool to learn first. For someone who can be easily distracted into rabbit holes, figuring out what to focus on can be overwhelming.
Automate or Become Obsolete

I took my adhoc research to the next level. I pulled a list of local tech companies as identified by this NCAA Bracket and randomly went directly to their career boards on their websites. I couldn’t find ANY companies that were looking for manual testers. In fact, most of my friends who have gone to smaller, startup-type environments have told me they must not only automate, but must handle the DevOps side of things as well.

Yes, you can still find manual testing roles, but mostly on legacy products. If you want to look forward, avoid obsolescence, and embrace automation.

Joe Nolan (@JoeSolobx) is a Mobile QA Team Manager with over 12 years of experience leading multi-nationally located QA teams, and is the founder of the DC Software QA and Testing Meetup.

Categories: Companies

Quality Excites, Gliwice, Poland, June 25 2016

Software Testing Magazine - Thu, 04/28/2016 - 14:00
Quality Excites (QE) is a free one-day conference on software testing and software quality that take place in Gliwice, Poland. It provides lectures and workshops for professional software testers who want to learn about the newest technologies and the best practices. All the talks are in Polish. Besides the software testing topics, the conference also covers the topics of software development techniques and Agile project management. In the agenda of Quality Excites you could find topics like “Jenkins: a friend of every tester”, “Automatic end-to-end tests for JavaScript applications”, “Pragmatic TDD”, “Robotium is coming”, “In the unit tests, do not solve problems with the tested code”. Web site: Location for Quality Excites: Gliwice, Poland
Categories: Communities

STAREAST is taking over Orlando! HPE is there to join in the action!

HP LoadRunner and Performance Center Blog - Thu, 04/28/2016 - 01:05

StarEast 2016-2.PNG

STAREAST is just around the corner! Keep reading to find out how to join the excitement next week in Orlando—even if you are joining from home.

Categories: Companies

Running Reports from the Surround SCM Source Tree Window

The Seapine View - Wed, 04/27/2016 - 16:30

If you use Surround SCM reports, there’s a pretty good chance you have at least one saved report that runs against files in whichever repository is currently selected in the Source Tree window. Reports configured this way are great because they provide the flexibility to access the same information about files in different repositories without requiring you to create and save multiple reports. However, they do require you to remember to select the repository that includes the files you want to report on before you open the Reports dialog to actually run them. Frankly, that part of the reporting process is not super intuitive so it can be easy to forget. Luckily, Surround SCM 2016 introduces a quick and simple way to set up shortcuts to run these reports directly from the Source Tree window. Here’s all you need to do:

1. Create a plug-in for the report you want to run from the Source Tree window.

In the Reports dialog, select the report and click Create Plug-in. The button is only enabled when a report configured to run against the <current selected> branch and <current selected> repository is selected. If you need to, you can add a new report with this setting or duplicate an existing report and change the branch/repository restriction in the new report.


Surround SCM creates the plug-in and displays a message with a little information about it for reference. Make note of the plug-in name and where it is saved in case you want to modify it later, but we’re going to stick with the default configuration right now.

2. Add the report menu item to the repository shortcut menu.

The plug-in loads automatically and a new shortcut menu item for the report is added to the user options. Choose Tools > User Options and select the Repository Menu category. In the Available menu items list, look for an item with the report’s name. Add that item to the Current menu items list, make any other changes to the items in the menu, and click OK.


3. Run the report from the Source Tree window.

Back in the Source Tree window, right-click a repository that includes files you want to report on and choose the report item.


The report runs, and you didn’t even have to open the Reports dialog first. How convenient is that?!

Interested in more custom shortcut menu items?

Be sure to check out our other blog post about creating and installing your own plug-ins to add custom shortcut menu items or entire menus for third-party application functionality to Surround SCM.

Categories: Companies

SonarSource City Tour, We Are Coming Near You

Sonar - Wed, 04/27/2016 - 14:51

Since we love touring and meeting our community of users, we’re setting out on the road once again, this time to more cities than ever! Over the next 6 months you’ll be able to see us and ask any questions you have, in more than 10 cities in Europe and the US.

This year, we are very excited to return to the City Tour to share with you all the news around the SonarQube platform, and show you our latest product: SonarLint, which allows developers to track quality of their code in real time as they type it. Very powerful!

Here is what will be covered at each stop of the tour:

  • The Leak Approach: a new paradigm to manage Code Quality
  • SonarQube 5.x series in demo
  • SonarQube integration to Microsoft ALM
  • SonarLint, the missing piece of the puzzle
  • Customer feedback
  • Sonar Analyzers and well-established standards
  • Roadmap for the platform
  • Roadmap for Sonar Analyzers

It will also be a great opportunity to meet other SonarQube users to share tips and tricks and discuss your experiences with the platform.

Is there something you would like to know or ask us but haven’t had the opportunity to do so? Now’s your chance! Sign up for the free event in your preferred city, and we’ll see you soon!

Registrations are open on our website, so pick the city you want, fill the form and you’ll be all set.

Join the conversation by using #SSCT2016 in all your tweets about the events.

See you soon !

Categories: Open Source

Knowledge Sharing

SpiraTest is the most powerful and affordable test management solution on the market today