The Blog
Software Testing SERVICES Testing Assessment & Roadmap ALM Assessment Test Strategy Agile Services Managed Services Automated Testing as a Service Sap Automated Testing Mobile App testing on-demand Automated Testing Dramatically improve your automation success Visual Studio Deployment Planning Service VS TFS Implementation VS TFS Migration VS Training Recruitment and resourcing Performance testing Training Microsoft Test Manager
Testing Assessment & Roadmap ALM Assessment Test Strategy
ALM Assessment
Test Strategy
Agile Services
Managed Services Automated Testing as a Service Sap Automated Testing Mobile App testing on-demand
Automated Testing as a Service
Sap Automated Testing
Mobile App testing on-demand
Automated Testing Dramatically improve your automation success
Dramatically improve your automation success
Visual Studio Deployment Planning Service VS TFS Implementation VS TFS Migration VS Training
Deployment Planning Service
VS TFS Implementation
VS TFS Migration
VS Training
Recruitment and resourcing
Performance testing
Training Microsoft Test Manager
Microsoft Test Manager
Industry FOCUS Property Services Financial Services Media Technology Retail Sector Energy Public sector
Property Services
Financial Services
Media
Technology
Retail Sector
Energy
Public sector
Knowledge CENTRE Videos What's new in Visual Studio 2012 for testing Visual Studio 11 How to Build Robust Coded UI Tests How can test tools help with the challenges of tomorrow's world? The journey from manual testing to automated testing using coded UI VS2010 - Test Impact, one giant leap for testkind! Visual Studio 2010 Test Professional Interview Latest News The benefits of adopting Agile nFocus RDT Case Study Released Microsoft Testing Stuff Sprint 7 nFocus MicroSponsor TestBash New White Paper: Agile & Quality News Archive 2014 2013 2012 2011 2010 2009 2008 2007 2006 2004 White Papers The benefits of adopting Agile Xamarin Vs Appium - which is the best automation tool for testing mobile device apps? The quality challenges associated with implementing agile and scrum Automation: 6 reasons why it fails and 6 things you must do Enhancing your Performance Test Strategy for Mobile Internet Access The Powerful Link Between Testing and Reputation Value Focused Testing Climbing Mount Reliability Case studies nFocus RDT nFocus BUPA nFocus Government Gateway nFocus SORCE nFocus Freight Transport Association nFocus Avelo
Videos What's new in Visual Studio 2012 for testing Visual Studio 11 How to Build Robust Coded UI Tests How can test tools help with the challenges of tomorrow's world? The journey from manual testing to automated testing using coded UI VS2010 - Test Impact, one giant leap for testkind! Visual Studio 2010 Test Professional Interview
What's new in Visual Studio 2012 for testing
Visual Studio 11 How to Build Robust Coded UI Tests
How can test tools help with the challenges of tomorrow's world?
The journey from manual testing to automated testing using coded UI
VS2010 - Test Impact, one giant leap for testkind!
Visual Studio 2010 Test Professional Interview
Latest News The benefits of adopting Agile nFocus RDT Case Study Released Microsoft Testing Stuff Sprint 7 nFocus MicroSponsor TestBash New White Paper: Agile & Quality
The benefits of adopting Agile
nFocus RDT Case Study Released
Microsoft Testing Stuff Sprint 7
nFocus MicroSponsor TestBash
New White Paper: Agile & Quality
News Archive 2014 2013 2012 2011 2010 2009 2008 2007 2006 2004
2014
2013
2012
2011
2010
2009
2008
2007
2006
2004
White Papers The benefits of adopting Agile Xamarin Vs Appium - which is the best automation tool for testing mobile device apps? The quality challenges associated with implementing agile and scrum Automation: 6 reasons why it fails and 6 things you must do Enhancing your Performance Test Strategy for Mobile Internet Access The Powerful Link Between Testing and Reputation Value Focused Testing Climbing Mount Reliability
Xamarin Vs Appium - which is the best automation tool for testing mobile device apps?
The quality challenges associated with implementing agile and scrum
Automation: 6 reasons why it fails and 6 things you must do
Enhancing your Performance Test Strategy for Mobile Internet Access
The Powerful Link Between Testing and Reputation
Value Focused Testing
Climbing Mount Reliability
Case studies nFocus RDT nFocus BUPA nFocus Government Gateway nFocus SORCE nFocus Freight Transport Association nFocus Avelo
nFocus RDT
nFocus BUPA
nFocus Government Gateway
nFocus SORCE
nFocus Freight Transport Association
nFocus Avelo
About nFOCUS Core Values Terms and conditions The Board Ross Lister Scott Summers John Qualtrough Danny Crone Microsoft relationship Testimonials Client list Partners Odin Grey Matter
Core Values
Terms and conditions
The Board Ross Lister Scott Summers John Qualtrough Danny Crone
Ross Lister
Scott Summers
John Qualtrough
Danny Crone
Microsoft relationship
Testimonials
Client list
Partners Odin Grey Matter
Odin
Grey Matter
Contact nFOCUS
The software testing process involves activities categorised into key stages during the evaluation of software quality.
Topics: Software Testing , Software Test Process
As England battled to victory against the Tunisian rugby team in their first fixture of the 2018 World Cup, many are praising the way in which the England manager Gareth Southgate has prepared his team. Team morale is at an all-time high, a team has been picked based on ability and potential and finally a formation/system that fits the players. Of course, this plan will need to change throughout the tournament – it will need to be Agile and adaptable to change. We can draw many parallels to the software development world and this article focuses on how an Agile Test Plan fits within the life-cycle of a project.
Topics: Software Testing , Agile Test Plan
If the Pentagon and the Whitehouse can both be hacked, then so can you. Now, please don’t think for a second that I think the members of the Pentagon and Whitehouse are in any way more intelligent or better than you (I’m convinced of quite the opposite – without even meeting you), but I am assuming they have pretty good cyber security.
Topics: Software Testing , Security Testing
To be very clear, business assurance is about providing companies with increased confidence in their business environment; meaning that they maintain improved quality and efficiency of their business processes and ensuring a high calibre of assurance that they’re in control of their business at all times.
Topics: Software Testing , Business Assurance
A test plan is used in the software testing process and sets out intentions regarding software testing activity targeting a software release implementation. Releases typically provide system changes and fixes to be implemented to enhance the business operations experience. We use test plans to help demonstrate that a system or product is developed as per the requirements and specifications.
Topics: Software Testing , test plan template
High user expectations and the risk of putting poorly performing code live makes performance engineering more important than it has even been. Fortunately, incremental change makes it easier to engineer system performance and build a workable process. For those doing DevOps , having administrators and technical subject matter experts as part of the delivery team have a much better ecosystem within which to deliver effective performance engineering.
Topics: Software Testing , Performance Engineering
What is the Internet of Things (IoT)? Well to simplify, it’s anything that can be connected remotely without wires; like the connection of your Amazon Echo, printers, heating systems, some vehicles and other home devices, along with medical/office equipment and of course your dog cams! Basically, anything that can collect and exchange data and information between the device and user. This technology allows the user to control devices remotely over a network – simple.
Topics: Software Testing , IoT Projects
Aging principles Within any software development team, testing involves investigation and analysis to identify product risks. Testers also provide information to stakeholders about the quality and complexity of testing so confidence levels are well understood. Depending on the methodology used, the success of a release may be largely based on the effectiveness of the test role.
In traditional methodologies, testers mainly contribute to delivery at the end of the process. If the testing phase only begins after analysis, design and implementation phases have been carried out, adapting to change becomes more difficult. Major issues found during this phase are usually so embedded, they are too risky to rework. If budgets and time pressures are a factor, it is always testing that suffers. Producing a high standard of testing becomes more and more challenging, and the blame culture starts to set in. Working in this way can cause communication issues between business analysts, developers, and testers where requirements are often misinterpreted. Siloed working in these phases can lead to an over the fence attitude, wasted effort and a lack of involvement in decision making. These cause motivation and frustration issues for the testers involved. Why Agile? The idea of delivering software in small, prioritised work items is to maximize value to the customer as early as possible. But things change. Customer expectations, difficulties with technology, new requirements, and changing priorities are all real complications that must be tackled on a regular basis. Short feedback cycles are vital so testers can react to ever-changing demands. Collaborating with business analysts, developers and stakeholders is the best way to make sure any re-planning is turned around quickly and efficiently, reducing waste. With better visibility of progress, gives time to plan for the feasibility of automation, non-functional requirements and test harnesses. This adds robust quality attributes, prioritised depending on their business value. In an Agile team, the tester role is utilised across the whole software life-cycle. Testing starts from day one of the project, and provides a platform to drive quality and influence team members to think likewise. Thinking from a customer point of view during refinement, the test focus includes asking questions, thinking about UX, personas, risks, impacts, workflows and testability early on when there is still time to change things. Being part of requirements analysis from conception ensures test planning is based on a concrete understanding of specifications, dealing with any ambiguity to avoid future rework. What makes Agile work? One of the benefits of Agile is that it is easy to adopt, in principle, if you were to implement the rituals and follow the rules. Frameworks like Scrum or Kanban have been provided. However, product maturity, dependencies on other teams, or even company politics means a templated approach does not suit all. Of all the Agile manifesto points, the key to making it work well is people over process. Each team has different personalities, skillsets, and specialists, which is why no two projects should be run or compared the same way. Agile gives the flexibility to create a working atmosphere where everyone adds value. It is the people that make Agile successful, not the rituals and processes. The goal is to build a culture that centres on collaboration and teamwork where everyone is responsible for quality. It takes away feelings of blame, pressure, and isolation that testers have frequently been the victim of in older methodologies. The experience of working together in synergy, creates an extremely slick and efficient team and testers thrive in a situation where there is respect and can contribute as equals. This results in the team analysing business value rather than testers trying to gain confidence in a squeezed time frame. For an Agile team to evolve requires trust. Things always go wrong during the project and people make mistakes. The important lesson is in how issues are dealt with. Empowering the team to learn from their own mistakes is rewarding, allows individuals to encourage each other and improve on estimates through experience. It is possible in a self-organising team, and works well when there is no micromanagement or multi layered hierarchy. Better Productivity Good testers love to learn. It is the basis of why we have a passion for testing. A self-managing and helpful team where everyone is working towards the same goal is a great motivator. Investigating and learning together with developers, and bouncing ideas against business analysts and other testers ultimately help to mitigate risks and reduces the overall cost of defects because they are captured and fixed much earlier during the development life-cycle. Modern Agile teams are focused on continuous integration and continuous delivery models. Multiple changes and quick turnaround of defects require testers to be at the centre of decisions. Testers are best placed in a project to understand overall changes and impacts, so reporting risks and test coverage to the business is a benefit for both testers and stakeholders. Business value in an Agile environment does not just include customer requirements. Creating a lean and efficient team helps to release within budget, allowing time to plan in knowledge transfer, self-learning and training. This investment improves knowledge that can be applied to future projects, and provides a longer-term benefit to the company without compromising delivery. This is good news for testers developing a T-shaped skill set - the capacity to work across multiple disciplines while specialising in one core skill. Since Agile working is fluid, testers need to be flexible enough to switch between a logical and creative mindset. Product knowledge gained through rapid test feedback and continuous self-development ultimately increases software quality. Exactly what Agile and Testing both aim to achieve.
Topics: Software Testing , Benefits of Agile
Regression testing is something that sounds so simple, so logical and an activity that should be obvious to what it entails. Yet time and time again, it is something that can cause problems for projects and software delivery. Usually in the time it takes to run the tests, inappropriate tests being used for regression or the very fact that there may be no regression suite to even execute.
Topics: Software Testing , Regression Testing
A functional requirement specifies a function that a system or system component must be able to perform. Probably the easiest way to explain ‘ non-functional ’ requirements is that they specify all the remaining requirements not covered by the functional requirements. Non-functional requirements specify the system’s ‘quality characteristics’ or ‘quality attributes’. Two products could have the same functions, but their attributes can make them entirely different products. A Rolls Royce has more or less the same functionality as a Lada but many different attributes!
Topics: Software Testing , Non-Functional Requirements
Welcome to the nFocus software testing blog. As thought leaders and technical innovators, we created this blog to distil our thoughts, ideas and musings on improving software quality.
Fill out the form below to receive future communications from nFocus including our latest:
Blog articles
White Papers
and plenty more!
Follow us on LinkedIn to see our latest content!
Software Testing (57)
Agile, (9)
Agile Test Strategy (8)
Test Management (5)
Testing (5)
Benefits of Agile (4)
DevOps and Testing (4)
Scrum (4)
TEST AUTOMATION BENEFITS (4)
Automated regression testing (3)
DevOps (3)
test automation (3)
Agile Test Plan (2)
IoT Projects (2)
Regression Testing (2)
Software Testing Techniques (2)
Test Manager (2)
software disasters (2)
software testing life cycle (2)
test plan template (2)
testing consultancy (2)
testing methodologies (2)
Agile Project Management (1)
Agile Testing Interview Questions (1)
Agile vs Scrum (1)
Business Assurance (1)
DevOps Release Management (1)
Future Tech (1)
GDPR (1)
Load Test Tools (1)
Load Testing Tools Comparison (1)
Load and Performance Testing (1)
Non-Functional Requirements (1)
Peformance Testing (1)
Performance Engineering (1)
Performance Testing Basics (1)
Performance Testing Entry and Exit Criteria (1)
Quality Assurance (1)
Quality Control (1)
Regression Testing Checklist (1)
Requirements Validation (1)
Risk Based Testing (1)
Security Testing (1)
Security Testing Strategy (1)
Software Failures (1)
Software Test Plan (1)
Software Test Process (1)
Software Testing Assessment (1)
Software Testing Consultancy (1)
Test Automation Approach (1)
Test Automation Frameworks (1)
Test Data (1)
Test Management Tools (1)
Test Tools (1)
Testing in DevOps (1)
halloween (1)
improve software testing (1)
internet of things (1)
load testing (1)
nFocus (1)
regression testing advantages (1)
regression testing and retesting (1)
Software Testing Services
Testing Assessment & Roadmap
Managed Services
Automated Testing
Visual Studio
Training
Industry
Knowledge Centre
Videos
Latest News
News Archive
Case studies
Designed and managed by Court Three Graphic Design Consultants Limited. Only our bets work carries this seal of approval.
© 2012- Court Three and nFocus Software Testing Limited. All rights reserved. The information on this website (and its associated Blog and Twitter feed) is for general interest only and should not be considered professional advice. Any action or inaction taken as a result of this information is not the responsibility of nFocus Testing. Professional advice should always be sought in relation to software testing. Company registration number (3942714)
Terms and conditions About nFocus Contact us Google+