Skip to content

Feed aggregator

Demo of Breaking the Environment Bottleneck

IBM UrbanCode - Release And Deploy - Wed, 03/04/2015 - 18:12

At Interconnect 2015, I presented a demo showing how a team could quickly identify a lack of test environments, spin up a new one and then start deploying changes through that environment towards production. Since then, I've had a number of requests from people who didn't make the session to see what I put together. So I posted an informal pass through the demo to Youtube for your viewing pleasure. Enjoy.

For a longer write-up on techniques for eliminating environment bottlenecks, check out this article.

Or learn more about UrbanCode Deploy with Patterns and UrbanCode Release.

Categories: Companies

TestTrack SDK Help – Now with More Information and Examples

The Seapine View - Wed, 03/04/2015 - 17:30

If you use the SOAP-based TestTrack SDK, you’ll be thrilled to know that we added lots more information and examples in the documentation to help you!

Here’s what’s new:

Operations

You can now view details for every available operation, including the parameters, return values, and examples written in C#.

SOAP Operation Example

Here is a list of all operations with links to individual topics for each operation.

Types

You can now view details for every data type, including fields, how they extend and are extended by other types, and where they are used.

SOAP Type Example

Here is a list of all types with links to individual topics for each type.

After you’ve had a chance to check out the improved help, be sure to let us know if you have any feedback.

Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon

Categories: Companies

expo:QA Survey Explores Software Testing Salaries

uTest - Wed, 03/04/2015 - 15:30

bannerYou may remember last year uTest conducted a survey on the state of our own community. In the same vein, the expo:QA conference, the meeting point for software testing and quality professionals in Spain and Europe, has its own survey out for the greater testing community. The 4th Annual 2015 Salary Survey of Software Testing Professionals is focused on a far more specific and polarizing topic — testing salaries.

According to expo:QA, “the study allows us to attain a new analysis of a constantly evolving sector and discover how the current economic situation has affected our profession.”

While the study in previous years wasn’t able to provide conclusive salary information for countries other than Spain, the survey is still open to all countries. By promoting it, uTest hopes to see — and encourages — responses from over the world so an interesting story can be told on potential salary disparities from country to country.

As an added incentive for testers, the first 200 to respond will be entered into a raffle for a €50 Amazon voucher to purchase the latest books in testing.

Testers can take the survey now until March 22. Additionally, stay tuned to the uTest Blog within the next couple of weeks to learn more about the expo:QA conference, and how uTesters can get discounted admission to the show.

expo:QA will take place in Madrid, Spain from June 8-11, 2015. Check out this event now and all other software testing events for 2015 at the uTest Events Calendar.

Categories: Companies

How to Automate Enterprise Application Monitoring with Ansible

In my last article, Top DevOps Tools We Love, I proclaimed the availability of deployment automation scripts for our Dynatrace products. Today, you will learn about the basic concepts behind Ansible, which will enable you to roll your own playbook for integrating insightful end-to-end monitoring with Dynatrace into every part of your enterprise application in under 60 seconds. Enterprise Applications and Distributed Architectures Enterprise […]

The post How to Automate Enterprise Application Monitoring with Ansible appeared first on Dynatrace APM Blog.

Categories: Companies

Visit Ranorex at the Next Leading Software Testing Events in the US

Ranorex - Wed, 03/04/2015 - 10:15
Ranorex is attending three leading software testing events in North America over the next two months. Take the advantage of these opportunities to meet the experts in test automation.

The events mainly focus on innovative solutions, discoveries and cutting-edge trends in software testing, including desktop, web and mobile testing. In addition to great presentations being given by top speakers from all over the world in combination with software testing workshops, you'll have also the chance to discuss your everyday test automation experiences and challenges with Ranorex professionals.

The software testing conferences will take place on the following dates:
  • March 30-April 2, 2015: Software Test Professionals Conference & Expo Spring  in San Diego, California
  • April 12-17, 2015: Mobile Dev + Test in San Diego, California
  • April 20-24, 2015: QUEST in Atlanta, Georgia

Don't miss the sessions presented by Jim Trentadue:
  • April 1, 2015: " How to Transform a Manual Testing Process to Incorporate Test Automation " at Software Test Professionals Conference & Expo Spring
  • April 23, 2015: " How Manual Testers Can Break into Automation " at QUEST
  • April 23, 2015: " Tranform the Manual Testing Process to Incorporate Automation " at QUEST

We're looking forward to seeing you there!
Categories: Companies

Jenkins User Conference – Save the Date

We have some exciting news to share with you! We have finalized most of the dates and locations for the 2015 Jenkins User Conference (JUC) World Tour.

Save the date(s):

  • US East (Washington DC): June 18-19
  • Europe (London): June 23-24
  • Israel: July 16 (ETA)
  • US West (Santa Clara): September 3-4

The big news? The JUC agenda has been expanded this year to cover two days! That means you get twice as many opportunities to learn how others are using Jenkins and to network with other Jenkins users.

CALL FOR PAPERS IS OPEN FOR ALL JUC CONFERENCES

We need JUC speakers! The Call for Papers is open now and you can apply here. This is an opportunity for YOU to give back to the community by sharing your Jenkins knowledge and success. Jenkins speakers contribute significantly to the overall JUC experience.

In return for speaking, you will receive free admission to the conference and fame/fortune within the Jenkins community. OK, we can’t guarantee the latter, but we can guarantee the former! Hurry and apply now, because the Call for Papers deadline for US East and Europe expires on March 22, 2015.

Not interested in speaking? Another way to contribute to the community is by letting us know who you want to hear from. Nominate or refer that amazing speaker and we’ll do the rest. Contact alytong13@gmail.com

JUC SPONSORSHIPS

Lastly, be a JUC sponsor. Any organization can do this – whether a vendor that sells into the Jenkins ecosystem or a company that has received value from Jenkins and wants to give back to the community. You can find out more here. (NOTE: JUC is not a moneymaking venture for the community – so sponsorships do make a difference.)

Categories: Open Source

Sonatype and Bamboo: Improving Your Builds

Sonatype Blog - Tue, 03/03/2015 - 22:01
Sonatype now provides native Atlassian Bamboo support to improve the quality of your build outputs. Sonatype provides instant analysis of open source components used in every Bamboo build and alerts development teams to any quality, license, or security issues identified. By catching the issues...

To read more, visit our blog at blog.sonatype.com.
Categories: Companies

TestPlant Releases eggPlant Network

Software Testing Magazine - Tue, 03/03/2015 - 19:21
TestPlant, the maker of the eggPlant range of software quality tools, has announced the launch of eggPlant Network. The product allows test and operations teams to emulate network conditions as part of the test and measurement of real user experience for digital services. The assessment of how network conditions affect the user experience is often overlooked.  There is a distinct gap in the armory of most enterprise “testing centers of excellence” for this element of testing application performance. The eggPlant range already includes eggPlant Functional for automated GUI and device testing ...
Categories: Communities

The Software Tester as a Designer

Software Testing Magazine - Tue, 03/03/2015 - 17:33
Software testing is an activity that has often been placed at the end of the software development life cycle, something that you did if there were some time left before the project deadline. In his book ” Scrum Shortcuts without Cutting Corners”, Ilan Goldstein explains that the software testers should be active since the beginning of the project. I believe that the core skill of a tester is actually that of design. Irrespective of who actually runs or implements a test, a seasoned professional tester will always be able to design ...
Categories: Communities

9 Steps to publishing a book on Amazon Kindle

The Social Tester - Tue, 03/03/2015 - 16:00

Last week I published my first book on Amazon – Remaining Relevant It was a great sense of achievement. I learned a lot about the self publishing industry and I learned a lot about myself. I never realised quite how...
Read more

The post 9 Steps to publishing a book on Amazon Kindle appeared first on The Social Tester.

Categories: Blogs

5 SharePoint Deployment Performance Health Checks: Beyond Making Sure Its Running

In my first blog I wrote about SharePoint System Performance Health Checks beyond looking at CPU and Memory Metrics. In this blog, I cover deployment related performance health problems that I always check when looking at a SharePoint Installation. Especially after deploying new hardware, new sites, pages, views, custom or 3rd party Web Parts (e.g: […]

The post 5 SharePoint Deployment Performance Health Checks: Beyond Making Sure Its Running appeared first on Dynatrace APM Blog.

Categories: Companies

Book Review: Waltzing with Bears

thekua.com@work - Tue, 03/03/2015 - 10:54

I read this book very early in my career, and I thought it would be useful to read it again as a refresher to risk management. Waltzing with Bears is a book that focuses on the identification and management of risks within the software industry. It’s filled with a number of stories answering the question, “Why should we care about risk?” as well providing a number of strategies and tools for handling risk.

Waltzing with Bears

Although a lot of the advice is still applicable today, I think it is true that some of the recommendations are commonplace today. They recommend, for instance, an incremental delivery approach to software (Hello agile software development!) without a specific reference to a methodology as a way of mitigating risk.

They also present the idea of estimate (un)certainty and using the idea to make better commitments to others. They also warn against default behaviour that is still rife in our industry: e.g. making a commitment to others based on an optimistic estimate hoping for a series of breaks when it is clearly high risk, which later leads on to the project death march, or a huge loss of quality.

Reading the book the second time around, I picked up a few other interesting models I don’t remember so clearly from the first time around including the use of probability profiles (a graph that shows the shape of our estimates and the uncertainties) to understand when and where to give estimated dates. There’s a useful section around risk-storming for people who have never been to a risk brainstorming session, but that wasn’t particularly new for me. Another one is the use of the Monte Carlo simulation for calculating the impact of risks. After reading that section however, I feel like I still don’t fully understand it and I would need to practice applying it for me to fully understand how that works.

Although the examples used in the book are relatively old now, there are still powerful stories about how people failed to manage risk, what they could have done instead and what the consequences were (e.g. Dallas Airport Baggage system!) I also like their practical experience shared when they talk about the cultural side of risk (e.g. how transparent or open and organisation is) and when it’s dangerous to share your view of risk. This sort of advice is often missed from books where the authors provide a very one-sided dogmatic approach without the consideration of contexts.

Overall this is an easily digestible book that introduces the idea and the importance of managing risk together with tools to help you achieve it, all set in the software industry context.

Categories: Blogs

Aruba, HP and optimizing your applications for the network

HP LoadRunner and Performance Center Blog - Tue, 03/03/2015 - 00:21

HP_Aruba_800x400.jpgToday, HP and Aruba Networks today announced a definitive agreement for HP to acquire Aruba, a leading provider of next-generation network access solutions for the mobile enterprise.

 

Let me walk you through this acquisition and tell you why I am so excited about what it means for end users and for HP Network Virtualization.

Categories: Companies

OSX Load Tester 6 Known Bugs and Workarounds

Web Performance Center Reports - Tue, 03/03/2015 - 00:10
As a long time Apple/Mac user I'm gratified to see our OSX download numbers creep up to 20%! Unfortunately with fewer people using the OSX version the first couple of releases had less outside bug reports than the Windows version, so thanks to all of the OSX users who've taken the time to send in bug reports so I can fix the issues.Related Posts:
Categories: Companies

uTest Partners with TechWell to Send One Lucky uTester to STAREAST in Orlando

uTest - Mon, 03/02/2015 - 21:33

Get your bags packed for some testing fun in the sun.logoStarEast

uTest is happy to announce that it has partnered with TechWell / Software Quality Engineering (SQE) to send one lucky uTester on a free trip to its flagship testing conference STAREAST!

What’s STAREAST?

STAREAST 2015 will be held May 3-8 in Orlando, FL, and is the premier event for software testers and quality assurance professionals—covering all your testing needs with 100+ learning and networking opportunities. Featured speakers for the 2015 edition include Dorothy Graham, Jason Arbon, Mike Sowers and Michael Bolton. In short, it’s bound to be another huge year at one of the biggest testing conferences in the United States.

How do you win?

Go to uTest.com/STAREAST and upload your best smartphone videos of why you want to go to STAREAST. Then, start sharing your video and collecting those votes! Share across LinkedIn, Twitter, Facebook… any social network you want to help get your video votes.

The uTest and SQE teams will pick one of the most voted videos to be the winner of the free trip!

The Grand Prize

One Lucky uTester will win a grand prize of over $5,000, including:

  • 5-Day Best Value package for STAREAST (Mon-Fri, includes 2 Tutorial Days, 2 Conference Days, and 1 Summit Day) ($3,095 Retail Value)
  • Five (5) nights at the conference hotel provided by TechWell / SQE ($1,125 Retail Value)
  • Meals for the duration of the conference
  • Reimbursement of airfare up to $500 provided by TechWell / SQE

Entry Period:
Between now, March 2 and Midnight, ET, March 26, 2015

Winners Announced:
The week of April 6, 2015

Before You Enter the Contest

Before you shoot that prize-winning video and pack your bags, please see the Official Rules for all details related to the SQE/uTest contest. Remember, this is only open to members of the uTest community. Not yet a uTester? Sign up for free today to gain access to free training, exclusive contests (like this one!), the latest software testing news, opportunities to work on paid testing projects, and networking with over 150,000 testing pros.

Good luck, and we hope to see you in Orlando!

ENTER NOW!
Categories: Companies

Test Automation for Behavioral Models

Testing TV - Mon, 03/02/2015 - 19:57
Model-based testers design abstract tests in terms of models such as paths in graphs. Then the abstract tests need to be converted to concrete tests, which are defined in terms of implementation. The transformation from abstract tests to concrete tests have to be automated. Existing model-based testing techniques for behavioral models use many additional diagrams […]
Categories: Blogs

Test Coverage at Google

Software Testing Magazine - Mon, 03/02/2015 - 19:43
Did you ever wonder how testing at Google looks like? What tools we use to help us out and how do we measure and act on test coverage? We will briefly describe the development process at Google, then focus on use of code coverage measurement and how we use code coverage to improve code quality and engineering productivity. In the end, we’ll present the vast amount of coverage data, spanning more than 100.000 commits, we have collected and some more widely applicable conclusions we have reached.
Categories: Communities

Clean Tests: Isolating the Database

Jimmy Bogard - Mon, 03/02/2015 - 19:35

Other posts in this series:

Isolating the database can be pretty difficult to do, but I’ve settled on a general approach that allows me to ensure my tests are built from a consistent starting point. I prefer a consistent starting point over something like rolled back transactions, since a rolled back transaction assumes that the database is in a consistent state to begin with.

I’m going to use my tool Respawn to build a reliable starting point in my tests, and integrate it into my tests. In my last post, I walked through creating a common fixture in which my tests use to build internal state. I’m going to extend that fixture to also include my Respawn project:

public class SlowTestFixture
{
    private static IContainer Root = IoC.BuildCompositionRoot();
    private static Checkpoint Checkpoint = new Checkpoint
    {
        TablesToIgnore = new[]
        {
            "sysdiagrams",
            "tblUser",
            "tblObjectType",
        },
        SchemasToExclude = new[]
        {
            "RoundhousE"
        }
    };

    public SlowTestFixture()
    {
        Container = Root.CreateChildContainer();
        Checkpoint.Reset("MyConnectionStringName");
    }

Since my SlowTestFixture is used in both styles of organization (fixture per test class/test method), my database will either get reset before my test class is constructed, or before each test method. My tests start with a clean slate, and I never have to worry about my tests failing because of inconsistent state again. The one downside I have is that my tests can’t be run in parallel at this point, but that’s a small price to pay.

That’s pretty much all there is – because I’ve created a common fixture class, it’s easy to add more behavior as necessary. In the next post, I’ll bring all these concepts together with a couple of complete examples.

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

Categories: Blogs

How To Get Started With Software Testing

Testlio - Community of testers - Mon, 03/02/2015 - 18:53

Software testing can be difficult.

To be an effective tester, you must be communicative, efficient, and patient.

If you’re an app developer and you’re looking to learn how to test your own app, you’re taking a great step forward.

In fact, 87% of app developers have found that their app’s performance had a significant effect on their ratings. If you’re looking to start testing, then your goal is to increase your app’s overall performance, which will increase your app store rating.

If you’re getting started with software testing, these are the five essentials:

 

1. Test Strategy

Organize your testing strategy | Get started with testing

Your goal is to be as effective as possible. A good test strategy lays out the overview of how to be effective.

To be a good tester, you need to find defects in your app. If you set up tests you know the app will pass, then you aren’t doing anyone any favors.

A test strategy tells you what type of testing would be best to do, the order in which to perform them, and the optimum amount of effort to make your testing effective.

When you’re setting up your first test strategy, you should focus on any features you prioritize as the most important.

If you’re doing this for a client, they should tell you what to focus on.

If you’re testing your own app, you’ll find you won’t know where to start or maybe there’s way too much to test. This is the purpose of a test strategy. Sit back, take a deep breath and try to prioritize your most important features.

Without a test strategy, you’ll end up spending the majority of your time on efforts with minimal results. After all, your users don’t care about the small bugs, they care about anything that impedes their experience.

 

2. Testing Plan

Plan Ahead with Test Planning | Get Started with Testing

A testing plan is made for your organizational purposes. This is where you layout what’s being tested, for how long, and by whom.

Think of this step as the path you would take to clear your conscious before releasing to the app store. On your testing plan, you need to not just lay out what is being tested, but also it’s necessary to state any dependencies each step would have on another. This way you won’t run into any surprises during your testing.

Your test strategy and testing plan are living and breathing documents. You will be continually updating them as you discover new bugs.

 

3. Test Cases

Pass Fail Test Cases | How To Get Started With Software Testing

Test cases are prepared as you are writing the program itself. Every feature or step in the program should have an expected result. For example if I sign into my account it should be expected that I land on the home dashboard every time.

To run this test, you input that information as a test case and if it ever comes to a point where that expected result does not happen, then you have a failed test case.

Test cases are designated on a pass/fail requirement.

Prioritize test case setups based on what you find is the most valuable part of your app. If you’re testing for a client, talk with them to see which area they find the valuable.

Except for a small amount of ad hoc testing, all of your test cases should be prepared before your actual software testing. This should be set up and thought of in parallel to your app development.

A good test case checks to make sure requirements are being met and has a good chance of uncovering defects.

 

4. Test Data

You don’t want to run tests on real user’s data, so it’s important to have a set of test data.

Frequent examples of test data are sets of names, addresses, product orders, or whatever information relevant to your app.

In your tests, you’ll be creating, updating, and deleting data. You don’t want to delete or update real data from real users from your app, so it’s important to have a set of test data that can be altered to make sure each one of your functions are working.

Test data development is done simultaneously with test case development.

 

5. Test Environment

As important as testing itself is the environment you test in.

Apps are likely to be multi-platform. It’s important you test on all devices the app is available on. This includes screen sizes of all types. If you’re creating an iOS app, you need to make sure you’re testing on all relevant Apple devices. This sounds very obvious, but it needs to be stated.

If you’re doing performance or usability testing, there are cases where you need to set aside whole rooms of devices to perform the required testing on the app.

Your testing environment needs to be set up and stated before you start testing. These are the materials and devices you and your team needs to confidently test apps.

Without the equipment and environment available, you cannot test your app with confidence.

 

Conclusion

Software testing is a growing field. As apps continue to eat the world, software testing will grow with it making sure each app is functioning adequately.

If you’re looking to get started testing your own app or a client’s, it’s important you take in these fundamental essentials of software testing:

  1. Test Strategy
  2. Testing Plan
  3. Test Cases
  4. Test Data
  5. Test Environment

In your time as a tester, you will run into difficulties such as undocumented requirements or a lack of organization. With these essentials in mind you will be able to approach your testing with clear focus.

 

The post How To Get Started With Software Testing appeared first on Testlio.

Categories: Companies

Next Gen DevOps and Software Testing

Yet another bloody blog - Mark Crowther - Mon, 03/02/2015 - 15:18
In his book, Next Gen DevOps, Grant outlines the historic path along which DevOps emerged and then describes how the way it is currently performed is fundamentally flawed. He describes a number of commonly experienced frustrations and inhibitors, both internal and external to the DevOps team, which people in other IT areas will unfortunately recognise. He shows how these impact the ability of the DevOps movement and its practitioners to drive forward their vision of what DevOps would ideally evolve into. Common issues other practice areas will recognise include; a lack of understanding of DevOps resourcing profiles by HR, a verbal agreement to the concepts of DevOps by senior management, but a fear to commit to the corporate and operational change needed to realise the vision, a continuing siloed approach that prevents the establishment of cross-functional, integrative product-based teams that are central to Grant’s view of modern DevOps practice.
Much of what Grant outlines in his book will ring familiar to software test practitioners. I and others have long espoused the value and indeed the criticality, of positioning software test practitioners as an embedded part of the ‘application development team’, ensuring cross-team process synergy1. A term I use in preference to names such as Dev team, the Test team, Ops team, Support team, etc. which serve only to reinforce the ‘silo’ us-and-them perspective. The concept of having these as teams who operate in a non-integrated way is less and less meaningful in context of today’s perspectives on efficient development approaches. Clearly defined practice domains remain important, the sheer scale of today’s IT profession requires a level of specialisation, but this is not the same as being siloed.

Taking this further, as we mature the adaptive, pragmatic, delivery focused approaches that are justifiably popular at this time, and possibly emerge into a post-Agile paradigm, approaches that were established in an era where predictive development models were overlaid onto functionaly siloed teams are, I would suggest, as good as irrelevant.
Services or Products?Except for the most trivial of application development related work, it simply isn’t possible to deliver anything meaningful, from a technology, business or market perspective, without cross-domain collaboration. This is true because of two key factors; a) large scale application complexity is now so high, that no single person or team can perform all practices effectively and, b) the integrated nature of technology and cross-over of practice areas means that practitioners in one field will already be working in a cross-domain manner.
However, we also need to shift perspectives and come back to another key point in Grant’s Next Gen DevOps book, that rings true for us as software test practitioners and ask; are we delivering a discrete set of software testing services in support of some application development work or are we providing a suite of testing practices, alongside other practice areas, in broader support for the delivery of a software product requested by the business?
If we think more broadly than our technology domains, considering also other domains across the wider business and reflecting on why we’re employed by the business, it will be evident that we’re not really engaged in testing some development output, but instead we’re testing an aspect of a product the business has requested. With even a trivial reflection, it’s apparent that all of these practice areas for given domains need to be drawn together to support not just application development, but to support product development from conception to retirement, in context not of the Software Development Life Cycle, but instead of the Product Development Life Cycle2.
ConclusionIn conclusion on these limited points; while Next Gen DevOps is proposed as a model for DevOps, it discusses many concepts that run parallel to our area of concern, that of the role of software testing practice in the broader business context when delivering software products requested by the business.
Mark.
--------------------------Learn More...
You can get a copy of Grants book on Amazon at: http://amzn.to/Zn2SKYIf you're on twitter, follow Grant at: https://twitter.com/grjsmith with hashtag #DevOpsWhile you're about it, pay a visit to his website over at: http://nextgendevops.com/ 
--------------------------


References
[1] Crowther, Mark, (2005) “Cross Team Process Synergy” [online] Available at: http://cyreath.co.uk/papers/Cyreath_Cross_Team_Process_Synergy.pdf[Accessed 02-mar-15]
[2] Crowther, Mark, (2009) “Life Cycles – Course 1, Session 1”, pp. 3-4

Categories: Blogs

Knowledge Sharing

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