Skip to content

Feed aggregator

Guiding Principles for Building a Performance Engineering-Driven Delivery Model

While recently attending a Dynatrace User Group in Hartford, I had the opportunity to sit in on a great presentation from a leading US insurance company as they explained their 3 year APM journey. I see a lot of these success stories, but this one was especially impressive. To see how they have refined their […]

The post Guiding Principles for Building a Performance Engineering-Driven Delivery Model appeared first on Dynatrace APM Blog.

Categories: Companies

Reach the next level - NEW Ranorex Advanced Training Course

Ranorex - Thu, 03/26/2015 - 11:00
Have you been looking for ways to increase the effectiveness of your automated tests using the Ranorex tools but haven’t had the time or experience to take advantage of some of the more sophisticated functionality Ranorex has to offer?

We are happy to announce a new offering how you can reach the next level of Ranorex competency with our advanced training course:

What:This 2-day course is geared towards existing Ranorex users who would like to gain a deeper understanding on key aspects like Object Recognition using RanoreXpath and Ranorex Spy, Ranorex Object Repository optimization, Ranorex API usage, plus much more! You will reduce maintenance and increase functionality while learning best practices to customize Ranorex and collaborate in a team environment. The content is technology agnostic and you will benefit from this training regardless of the type of UI you are automating with Ranorex.When:The course dates are April 28-29, 2015 and June 16-17, 2015. Stay tuned for additional dates later in 2015.Where:At the Ranorex North American Headquarters in Clearwater, FL. This will allow us to provide a more personal interaction and attention to each attendee to cover advanced topics. The advanced training course will not be offered online. Instead, we offer you the opportunity to visit the Sunshine state and are hosting the training at our corporate office. This allows you to engage with the Ranorex team for a more individual learning experience through a combination of presentations, hands-on exercises and group discussions.Cost:Registration for the 2-day training is $1,395 per person. Space is limited, so reserve your seat now!Registration: Right this way please or contact our sales team for a quote.
Additional information can be found in the course description and curriculum . Please be aware of the necessary prerequisites to attending this training course.



Please contact us at sales.us@ranorex.com with any questions you may have.
We look forward to seeing you in one of our advanced classes soon!

Look at the schedules for additional workshops in the next few months:

Categories: Companies

Pulse Roadmap Update

a little madness - Thu, 03/26/2015 - 05:30

Long time users of our Pulse Continuous Integration Server would know that we don’t believe in posting long-term roadmaps. They just never reflect a changing reality! But we have always been happy to discuss features with customers, including keeping our issue tracker (creaky old version of Jira that it is) completely open for all to see and contribute. In that spirit I’d like to talk a little about where we’re heading with Pulse in the near term, the bit that can be predicted, in a format more digestible than disparate issues.

The next version of Pulse (as yet unnamed), will have updates focused on a few areas:

  1. Upgrades of underlying libraries including Equinox, Spring, Spring Security, Hibernate, Jetty, Quartz, EhCache and more. If you haven’t seen a lot of visible changes reported recently this is why: these upgrades have occupied the first part of this development cycle. These are truly the most boring of all changes, which we hope you won’t notice directly at all! What you will notice, though, is a payoff of this strong foundation over time.
  2. Major updates to the administration interface. The interface works well enough at the moment but could be improved in a couple of key areas: discoverability and efficiency. Key goals for these updates include:

    • Improving the visibility of the most commonly-used configuration via overview pages.
    • Making it easier to discover what is overridden (via templating) and where.
    • More efficient navigation, especially through the template hierarchy.
    • Modernisation to take advantage of HTML 5 (which the current interface predates).

    These changes are big enough to warrant a dedicated blog post at a future point.

  3. Improved visibility of the build environment. When builds fail in curious ways the culprit is often a small difference in the environment. Pulse currently publishes environment information via implicit env.txt artifacts, but these haven’t kept up to date with the variety of options Pulse now gives for specifying build properties.
  4. Improvements to the Windows experience. In 2.7 work was done to improve Windows service support, but more could be done to streamline the setup process in particular.

As always we will also be working on dozens of smaller improvements and suggestions from our user base, most of which fall under one of:

  • UI polish, especially in the reporting interface.
  • Increased flexibility of project and build configuration.
  • Updated support for modern versions of build tooling.

Customers are more than welcome to connect with us via our support email, support forum, or issue tracker to discuss these and other changes you’d like to see in Pulse!

Categories: Companies

Registration for JUC 2015 is Open!

It's that time of the year again: 2015 Jenkins User Conference Registration is OPEN for all cities. This year, we are making some changes to JUC — JUC will be a two-day event in three out of the four cities across the globe. You will get opportunities to network with other users and developers in the community, learn more about how other people are using Jenkins and attacking broader continuous delivery problem. As always, we love to meet & talk to you to learn what you are doing with Jenkins. To get the sense of how JUC is like, take a look at our past JUC reports like this and this.

Early Bird pricing for JUC tickets is available until May 1.

You can learn a lot more information here about the 2015 Jenkins User Conference World Tour. As always, we are tweaking JUC to make it better, based on feedback. I'll post about those in coming months. Make sure to follow or tweet at @jenkinsconf to stay up to date on JUC news or to share which JUC you will be attending!

See you there!

Categories: Open Source

Registration is Open for JUC 2015!

Attend THE conference for Jenkins users, by Jenkins users.Register and Learn More. Early Bird rate ends May 1!
 In the past, the Jenkins User Conference has been a one-day event, but this year for the first time ever it will be a two-day event in three cities, providing you with more content and more networking opportunities with more Jenkins users! (Refer to the graph below to see just how many attendees are expected.)

The main focus of JUC is the use of Jenkins for continuous integration (CI) and continuous delivery (CD) as the fundamental best practice for enterprise software delivery. All JUC presenters are experienced Jenkins developers, build managers, QA, DevOps practitioners, IT managers/executives, architects and IT operations who are luminaries within the Jenkins community. They represent the many organizations around the world that are leveraging the use of Jenkins within the software delivery lifecycle.
In 2014, the community saw an 80% increase in attendance
over 2013. This year, 800-1000 attendees are expected in
each city!
We welcome you and other leading Jenkins developers, QA, DevOps and operations personnel to the Jenkins User Conference World Tour. As the organizing sponsor of the Jenkins User Conferences, CloudBees has helped the community grow the Jenkins User Conferences worldwide over the last four years.

In 2015, the World Tour will bring together the full strength of the Jenkins community—now over 100,000 installations strong—and the ever expanding Jenkins partner ecosystem, allowing attendees to learn, explore, network face-to-face and to shape the next evolution of Jenkins development. Kohsuke Kawaguchi will kick off the event with a keynote address and lead us into the two-day conference. Attend a JUC to get the knowledge you need to make your current and future Jenkins projects a success.
Categories: Companies

Testing Angular Applications

Software Testing Magazine - Wed, 03/25/2015 - 17:47
Ari Lerner believes that testing is a core aspect of development, that they cannot be separated from one another, that they are one in the same. This talk is about Angular, and is specifically about testing the Angular JavaScript framework, but the approaches discussed are universal to front-end applications alike. This talk try to anwers the following questions about the testing of Angular.js applications: * What does it mean to test? * Why test? * What is good testing technique? * How can we test every component of our application? Conference producer: http://forwardjs.com/ Video producer: https://thenewcircle.com/
Categories: Communities

uTest Announces Winning Testers of the Quarter for Q1 2015

uTest - Wed, 03/25/2015 - 17:12

uTest is proud to announce the first 2015 Testers of the Quarter for Q1!badgeTesterOfQuarter

Our quarterly community recognition program exists solely to recognize and award the rock stars of our global community. Testers recently concluded voting for their peers and mentors, recognizing their dedication and quality work in various facets of uTest participation including test cycle performance, course writing and blogging, and Forums participation.

In addition to the winners below, you can also view their names now in our uTest Hall of Fame. Without further ado, here are the Q1 2015 Testers of the Quarter at uTest:

Outstanding Forums Contributors
David Petura, Czech Republic
David Shakhunov, United States
Bhudev Dalal, India

Outstanding Content Contributors
George McConnon, United Kingdom
Evan Hjelmstad, United States

Outstanding TTLs
George McConnon, United Kingdom
Nadezda Jerjomina, Latvia
Linda Peterson, United States

Outstanding Testers, TTLs’ Choice
Matthew Duval, United States
Milos Dedijer, Serbia

A big congratulations to all of those that had the distinction of being recognized by their peers for the first 2015 edition of Tester of the Quarter. We even had some multiple-quarter-and-category winners lighting it up this quarter, and continuing to be rockstars in the eyes of their peers! Additionally, while their names may not be here, there were also countless other testers that got individual praise along the way — their hard work did not go unnoticed.

Leave your congratulations in the Comments below, or visit the Forums to see the full announcement…along with some of the tester praise that led to these distinctions!

The post uTest Announces Winning Testers of the Quarter for Q1 2015 appeared first on Software Testing Blog.

Categories: Companies

Master the Essentials of UI Test Automation Series: Chapter Six

Telerik TestStudio - Wed, 03/25/2015 - 14:00
Chapter 6: Automation in the Real World So here you are: ready and raring to get real work done. Hopefully, at this point, you're feeling excited about what you've accomplished so far. Your team has set itself up for success through the right amount of planning, learning and prototyping. Now it's time to execute on what you've laid out. Remember: your best chance for success is focusing on early conversations to eliminate rework or waste, and being passionate about true collaboration. Break down the walls wherever possible to make the mechanics of automation all that much easier...
Categories: Companies

Making Sure New TestTrack Items are Immediately Assigned

The Seapine View - Wed, 03/25/2015 - 09:00

Have you ever wondered if there was a way to make sure new items are assigned to a user as soon as they are added to TestTrack, so your project does not contain a large number of items that are not assigned? Here are a couple of solutions that can help you do just that.

Note: The following solutions use trigger rules to make sure new items added are assigned to users. Issues are used in the example configurations, but the information can also be used to assign new requirements, documents, and test cases.

Solution 1: Create a trigger that assigns items based on the value set in a custom assignment field

This solution uses a trigger rule to automatically assign new issues based on the value set in a custom field.

First, create a custom assignment field that lets users select who to assign new issues to. Because issues will be assigned to different users as they move through the workflow, consider using a field name that clearly indicates the field is only used to set the initial assignment for new issues. After the field is added, you will update the security privileges to make sure it is only available when users add issues. More on that later.

The assignment field should be a Pop-Up Menu field that uses the Users value list. Display the field on the Main Issue Window so users can easily see it and be sure to select Supports multiple selection if you want users to be able to assign new issues to more than one person.

AddCustomFieldAssignedTo

After the assignment field is added, create a trigger that enters an Assign event when new issues are created and uses the value set in the assignment field to determine who to assign them to. In the Add Trigger Rule dialog box, leave the Precondition setting as Not Filtered so the trigger applies to all new issues. Click the Trigger When tab to specify that the trigger should run when a new issue is created and before it is saved. Click the Actions tab to add an Enter event action. The trigger should enter an Assign event and assign the issue to the list of users selected in the assignment field. The following screenshot shows the complete trigger summary.

EnterAssignEventTriggerSummary

Next, update field security for the assignment field in all security groups. Users should have read/write privilege to the field when adding new issues, but the field should be hidden when editing issues to prevent users from using the field instead of a workflow event to assign updated items.

Finally, make the assignment field required so users must select who to assign new issues to. If users do not set the field when adding issues, they are prompted to set it before saving.

When all the changes are saved, add a new issue to test the required assignment field and trigger. Enter all the required issue information except the assignment setting and click Add. You should see a message indicating that you cannot save the issue because the assignment field is required.

AddIssueAssignToRequired

Select a user in the assignment field and then click Add again. The issue is added and automatically assigned to the selected user. When you view or edit the issue, you can see the Assign event was added to the issue and the initial assignment field is hidden.

ViewIssueAssignTrigger

Solution 2: Create a trigger that prevents users from adding new items without assigning them first

This solution uses a trigger rule to make sure new issues are assigned through the workflow to the appropriate user before they are saved.

First, create a trigger that applies only to issues that are not assigned. In the Add Trigger Rule dialog box, on the Precondition tab, click Create Filter. The filter should use the Currently Assigned To restriction to select issues that have an unknown assignment.

AddFilterNotAssigned

After selecting the precondition filter for the trigger, click the Trigger When tab to specify that the trigger should run when a new issue is created and before it is saved. Finally, click the Actions tab to add a prevent action that displays a message to users instructing them to enter the Assign event before saving new issues. The following screenshot shows the complete trigger summary.

PreventAddingWithAssignmentTriggerSummary

Next, make sure the initial state in the issue workflow allows users to add an Assign event. To check this, choose Tools > Administration > Workflow. Select Issues as the Type and click the Transitions tab. The initial state for new issues should have Assign set as an available transition.

ConfigureWorkflowIntitalStateAssignTransition

When all the changes are saved, add a new issue to test the trigger. Enter all the required issue information and then click Add. You should see the message indicating that you cannot save the issue because you did not enter an Assign event.

AddIssueCannotSaveUnassignedIssue

Assign the issue and then click Add again. The issue is added and assigned to the selected user.

Thanks to Gordon Alexander, Seapine Software solutions specialist, for providing the second solution mentioned in this post.

The post Making Sure New TestTrack Items are Immediately Assigned appeared first on Blog.

Categories: Companies

Learn How to Find Highly Valuable Bugs

uTest - Tue, 03/24/2015 - 20:01

uTest University recently hosted a “How to Find Highly Valuable Bugs” live webinar, led by Test Team Leads (TTLs) Dave D’Amico and Todd Miller. Dave’s experience in software support/system administration and Todd ‘s perspective as a former test manager on the customer side provided some unique insights into the bug hunting and bug reporting process.

Some tester tips from the webinar include:

  • It is important to know the customer’s product life cycle and where your testing fits in to that life cycle.
  • Know the scope and known issues for your test cycle so that you recognize a high value bug when you encounter one.
  • Monitor the cycle and see what other testers are submitting. Are there traits to the approved bugs that you adopt to improve your own reporting?
  • Every cycle is unique, so a tester needs to adapt based on the information given in each new cycle.
  • Context builds value! Bug reports often get sent to people on the customer side who were not part of the test cycle. Make sure your bug report is written so that everyone can understand it.

In this excerpt from the webinar, Dave and Todd talk about the concept of “high value” and why that can be different between different customers and test cycles. You can also view the full recorded webinar.

 

For more courses, how-tos and webinars, check out uTest University, your source for free software testing training.

Not a uTester yet? Sign up today to comment on all of our blogs, and gain access to free training, the latest software testing news, opportunities to work on paid testing projects, and networking with over 150,000 testing pros. Join now.

The post Learn How to Find Highly Valuable Bugs appeared first on Software Testing Blog.

Categories: Companies

This Is The Only Time To Ask For App Reviews

Testlio - Community of testers - Tue, 03/24/2015 - 19:33

Do you like me?

Unless you know me or are a steady reader of this blog I can’t imagine you would be ready to answer that question.

In fact, you’re likely leaning towards no.

It’s obvious why people don’t ask that question when they first meet someone.

Despite this being so common, I see apps asking me to review them in the app store within the first 10 minutes.

New users are delicate. The slightest nudge in the wrong direction can turn them off from your app forever. In fact, 80-90% of users delete an app after using it just once.

However it is important to ask your users to rate your app on the app store. Few of your users will be proactive enough to go to the app store and rate it on their own unless you have a stand out app.

Your users need to be pushed to rate your app. Otherwise it will never show up in results and potential users will be reluctant to try it out.

Whenever you ask your users to review your app, the timing needs to make complete sense. If you don’t give them enough time to play with your app and learn how it works, you end up rushing them. When you rush your users to make a decision, it will leave a bad taste in their mouth. When you leave a bad taste in your user’s mouth, they will translate that foul taste in as an app review.

 

 

KissMetrics App Reviews Image from Kissmetrics

There is only one situation where it makes sense to ask for an app review from your user.

After they experience the core value of your app.

This is the only time I have found where it makes sense to ask a user to rate your app if you’re looking for constructive feedback and/or positive reviews.

This is important if you want to sustain high app store ratings and improve your app.

If you’re creating a messaging app, ask your users to rate your app after they’ve sent at least 20 messages. By then it should be clear that your app generates some sense of value for them.

If you’re creating a social network, then ask people to review your app after they’ve added a few of their friends and interacted with them. You wouldn’t ask someone to rate your app if they’ve never used it.

 

“But what if I want to use the app store to see how I can improve my app?”

Your app store reviews is not a support center.

If your users have a problem with your app, don’t give them the option to release their frustration on your app store rating. Instead, make a prompt come up asking them to explain their frustrations. Keep it private. Not everyone in the world needs to know that your app is buggy.

In fact, the best customers are the ones with the problems. By giving your users an avenue to express their frustrations, you open an opportunity to turn a frustrated user into an evangelist by providing exceptional customer service.

If you’re looking to turn frustrated users around I recommend using Helpshift. Their product creates a very simple instant communication avenue with your users.

 

Those who like you give you five stars. Those who love you give you four.

A common mistake I see when founders are reading their app reviews is focusing too much on one and five star ratings.

App reviews on the app store

I have a problem with anything using the Likert scale because you end up with a U-shaped results. You have a lot of five star ratings, a lot of one star ratings, and very few of everything in between.

One star ratings are almost useless. The only time they make sense is when there is a huge flaw such as frequent crashing. Other times they’re a user who had a bad experience at no fault of your app. For example, this person gave a waterfall mapping app a one star review because they got stung by wasps.

One star ratings generally aren’t helpful. Five star ratings aren’t much better.

Thoughtful five star reviews are great for finding out what users love about your app. While this may be great for your team’s focus, it doesn’t give you much in terms of improvement or news.

Users who rate your app between 2-4 stars want to see you succeed. These are the reviewers that give the thoughtful constructive criticism.

They will tell you what they like, what they don’t like, and what they think could be done for improvement.

 

Conclusion

If you’re asking your users to rate your app, make sure you’re doing it in a timely manner. Don’t rush them to form an opinion when they haven’t had enough time to experience the benefit of the app.

One star and five star app reviews will not be as helpful for information to improve your app. Instead focus on the 2-4 star reviews.

When do you ask your users to rate your app? How has it worked out for you so far? Tweet your answer to www.twitter.com/willietran_ or reply in the comments below.

The post This Is The Only Time To Ask For App Reviews appeared first on Testlio.

Categories: Companies

Vector Software Adds Covered By Analysis Capability

Software Testing Magazine - Tue, 03/24/2015 - 18:20
Vector Software, a provider of solutions for embedded software quality, has announced the availability of VectorCAST/CBA (Covered By Analysis) which allows users in regulated industries to augment measured coverage with manual analysis to achieve the mandated 100% code coverage. VectorCAST/CBA is available as an add-on for all VectorCAST products, and provides an intuitive editor which allows users to provide analysis for statements, branch outcomes, or MC/DC pairs depending on the coverage level. The ability to combine Coverage Analysis data sets with measured code coverage from unit, integration, and system testing, provides ...
Categories: Communities

Clean Tests: Isolation with Fakes

Jimmy Bogard - Tue, 03/24/2015 - 17:58

Other posts in this series:

So far in this series, I’ve walked through different modes of isolation – from internal state using child containers and external state with database resets and Respawn. In my tests, I try to avoid fakes/mocks as much as possible. If I can control the state, isolating it, then I’ll leave the real implementations in my tests.

There are some edge cases in which there are dependencies that I can’t control – web services, message queues and so on. For these difficult to isolate dependencies, fakes are acceptable. We’re using AutoFixture to supply our mocks, and child containers to isolate any modifications. It should be fairly straightforward then to forward mocks in our container.

As far as mocking frameworks go, I try to pick the mocking framework with the simplest interface and the least amount of features. More features is more headache, as mocking frameworks go. For me, that would be FakeItEasy.

First, let’s look at a simple scenario of creating a mock and modifying our container.

Manual injection

We’ve got our libraries added, now we just need to add a way to create a fake and inject it into our child container. Since we’ve built an explicit fixture object, this is the perfect place to put our code:

public T Fake<T>()
{
    var fake = A.Fake<T>();

    Container.EjectAllInstancesOf<T>();
    Container.Inject(typeof(T), fake);

    return fake;
}

We create the fake using FakeItEasy, then inject the instance into our child container. Because we might have some existing instances configured, I use “EjectAllInstancesOf” to purge any configured instances. Once we’ve injected our fake, we can now both configure the fake and use our container to build out an instance of a root component. The code we’re trying to test is:

public class InvoiceApprover : IInvoiceApprover
{
    private readonly IApprovalService _approvalService;

    public InvoiceApprover(IApprovalService approvalService)
    {
        _approvalService = approvalService;
    }

    public void Approve(Invoice invoice)
    {
        var canBeApproved = _approvalService.CheckApproval(invoice.Id);

        if (canBeApproved)
        {
            invoice.Approve();
        }
    }
}

In our situation, the approval service is some web service that we can’t control and we’d like to stub that out. Our test now becomes:

public class InvoiceApprovalTests
{
    private readonly Invoice _invoice;

    public InvoiceApprovalTests(Invoice invoice,
        SlowTestFixture fixture)
    {
        _invoice = invoice;

        var mockService = fixture.Fake<IApprovalService>();
        A.CallTo(() => mockService.CheckApproval(invoice.Id)).Returns(true);

        var invoiceApprover = fixture.Container.GetInstance<IInvoiceApprover>();

        invoiceApprover.Approve(invoice);
        fixture.Save(invoice);
    }

    public void ShouldMarkInvoiceApproved()
    {
        _invoice.IsApproved.ShouldBe(true);
    }

    public void ShouldMarkInvoiceLocked()
    {
        _invoice.IsLocked.ShouldBe(true);
    }
}

Instead of using FakeItEasy directly, we go through our fixture instead. Once our fixture creates the fake, we can use the fixture’s child container directly to build out our root component. We configured the child container to use our fake instead of the real web service – but this is encapsulated in our test. We just grab a fake and start going.

The manual injection works fine, but we can also instruct AutoFixture to handle this a little more intelligently.

Automatic injection

We’re trying to get out of creating the fake and root component ourselves – that’s what AutoFixture is supposed to take care of, creating our fixtures. We can instead create an attribute that AutoFixture can key into:

[AttributeUsage(AttributeTargets.Parameter)]
public sealed class FakeAttribute : Attribute { }

Instead of building out the fixture items ourselves, we go back to AutoFixture supplying them, but now with our new Fake attribute:

public InvoiceApprovalTests(Invoice invoice, 
    [Fake] IApprovalService mockService,
    IInvoiceApprover invoiceApprover,
    SlowTestFixture fixture)
{
    _invoice = invoice;

    A.CallTo(() => mockService.CheckApproval(invoice.Id)).Returns(true);

    invoiceApprover.Approve(invoice);
    fixture.Save(invoice);
}

In order to build out our fake instances, we need to create a specimen builder for AutoFixture:

public class FakeBuilder : ISpecimenBuilder
{
    private readonly IContainer _container;

    public FakeBuilder(IContainer container)
    {
        _container = container;
    }

    public object Create(object request, ISpecimenContext context)
    {
        var paramInfo = request as ParameterInfo;

        if (paramInfo == null)
            return new NoSpecimen(request);

        var attr = paramInfo.GetCustomAttribute<FakeAttribute>();

        if (attr == null)
            return new NoSpecimen(request);

        var method = typeof(A)
            .GetMethod("Fake", Type.EmptyTypes)
            .MakeGenericMethod(paramInfo.ParameterType);

        var fake = method.Invoke(null, null);

        _container.Configure(cfg => cfg.For(paramInfo.ParameterType).Use(fake));

        return fake;
    }
}

It’s the same code as inside our context object’s “Fake” method, made a tiny bit more verbose since we’re dealing with type metadata. Finally, we need to register our specimen builder with AutoFixture:

public class SlowTestsCustomization : ICustomization
{
    public void Customize(IFixture fixture)
    {
        var contextFixture = new SlowTestFixture();

        fixture.Register(() => contextFixture);

        fixture.Customizations.Add(new FakeBuilder(contextFixture.Container));
        fixture.Customizations.Add(new ContainerBuilder(contextFixture.Container));
    }
}

We now have two options when building out fakes – manually through our context object, or automatically through AutoFixture. Either way, our fakes are completely isolated from other tests but we still build out our root components we’re testing through our container. Building out through the container forces our test to match what we’d do in production as much as possible. This cuts down on false positives/negatives.

That’s it for this series on clean tests – we looked at isolating internal and external state, using Fixie to build out how we want to structure tests, and AutoFixture to supply our inputs. At one point, I wasn’t too interested in structuring and refactoring test code. But having been on projects with lots of tests, I’ve found that tests retain their value when we put thought into their design, favor composition over inheritance, and try to keep them as tightly focused as possible (just like production code).

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

Categories: Blogs

Free Web Load Testing Services

Software Testing Magazine - Tue, 03/24/2015 - 17:15
The software development trend that shifts the target platform from the desktop to web, cloud and mobile applications has fostered the development of load testing services on the web. It is an obvious option to use web-based load testing tools for applications that can be accessed by web users. This article presents the free offers from commercial web load testing services providers. We have considered in this article only the tools that provides a load testing service that we define as the ability to simulate the access by multiple users on ...
Categories: Communities

Jason Huggins: Fixing HealthCare.gov, One Test at a Time [MEETUP]

Sauce Labs - Tue, 03/24/2015 - 17:00

jason-hugginsYou may recall that our co-founder Jason Huggins took a leave of absence to help fix HealthCare.gov. He’ll be back on April 21 to talk about his experiences there at the next Selenium Meetup in San Francisco. RSVP before it fills up! Info below.

Date + Time: Tuesday, April 21, 2015 at 6:30 PM

Location: If (we): 848 Battery Street, San Francisco, CA

ABSTRACT

In late 2013, Selenium creator Jason Huggins joined President Obama’s “tech surge” team to help fix HealthCare.gov. In D.C. during the height of the crisis in November and December 2013, Jason had a behind-the-scenes view into a unique period in American history when a website’s quality (or lack thereof) had the attention of the nation, the press, the President, and Congress.

In this talk, Jason will share some of his stories from the HealthCare.gov turnaround and the “HealthCare 2.0″ effort in mid-2014. Jason will talk about the newly created U.S. Digital Services and how it was created out of the original HealthCare.gov crisis. He’ll also cover the U.S. Digital Services Playbook and what the role of automated testing and deployment will be in future U.S. Government projects.

Lastly, Jason will talk about opportunites for how Silicon Valley can help government build effective digital services in the future.

BIO

Jason is a software engineer living in Chicago. He started the Selenium project in 2004 at ThoughtWorks. He later joined Google to work on large-scale web testing for Gmail, Google Maps, and other teams. He left Google to co-found Sauce Labs as CTO to create a cloud-based Selenium service. In late 2013, Jason took leave from Sauce to help with the HealthCare.gov turnaround. He is also the creator of Tapster, a mobile app testing robot that’s been featured in Popular Science, Wired,Tech Crunch, and the MIT Technology Review.

AGENDA

6:30: Dinner & networking

7:00: Announcements

7:10: Speaker

8:45: Lights out!

RSVP today!

Categories: Companies

Significance of alwaysRun=true @Test annotation property.

Testing tools Blog - Mayank Srivastava - Tue, 03/24/2015 - 16:15
alwaysRun=true property informs the system that TestNg should run the test method if depends on @Test method fails also. Basically it helps to achieve the soft dependency, the feature of TestNG which helps to execute the testng test methods in order. Below is the code example: So above code states that system will execute the […]
Categories: Blogs

How to Launch Chrome browser with Selenium WebDriver?

Testing tools Blog - Mayank Srivastava - Tue, 03/24/2015 - 15:17
Before thinking how we can run the our application on Chrome browser, download the ChromeDriver from here. To lunch chrome browser with Selenium Webdriver takes less than a minute and 3 lines of code. So here we go- System.setProperty(“webdriver.chrome.driver”, “D:\\Chrome_Driver\\chromedriver.exe”); WebDriver driver=new ChromeDriver(); driver.get(“http://seleniumeasy.com/&#8221;);
Categories: Blogs

5 Tips to Improve SharePoint Web Part Performance

In a recent SharePoint Performance PerfBytes Episode Mark Tomlinson, Howard Chorney and I discussed SharePoint Performance based on my blog posts System Performance Checks and SharePoint Deployment Checks. We soon concluded that Web Parts – being one of the key concepts in SharePoint – ultimately decides whether your SharePoint sites scale, perform fast and will […]

The post 5 Tips to Improve SharePoint Web Part Performance appeared first on Dynatrace APM Blog.

Categories: Companies

Quality Excites, Gliwice, Poland, May 30 2015

Software Testing Magazine - Tue, 03/24/2015 - 12:08
Quality Excites (QE) is a free one-day conference on software testing and software quality that 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 ...
Categories: Communities

Guided Start for Recording

Ranorex - Tue, 03/24/2015 - 11:45
Ranorex 5.3 introduces a guided start for recording, increasing the simplicity and robustness of your automated testing.

This functionality allows a quick start in test automation for first time users. Ranorex automatically prepares the system under test by choosing the technology (desktop, web, mobile) that your test is based on. Guided Recording for Automated Testing

The main features of the Ranorex Test Recorder include:
  • Capture and replay of any kind of user action
  • Maintainable recordings via the actions table editor
  • Integration of Ranorex repositories for object-based automation
  • Validation mode for use during recording sessions
  • Generation of Ranorex report files for every replay
  • Generation of C# and VB.NET source code

Start your robust test automation project now – try the new guided start for recording!
Categories: Companies

Knowledge Sharing

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