So often many of us who have been in IT for a number of years think of software services as something getting done off shore by a large staff focused on their screens with their ‘blinders’ on. This could not be further from the truth. We have many extraordinary software development experts today focused primarily on the customer experience while using the ever improving technologies that make sure customers are no longer frustrated with websites being down, product availability advertised being untrue, or any number of issues we all encounter that causes our blood pressure to rise.
Tag Archives: Bridge360
An Effective Way to Break Down and Track User Stories
Fake News – Java is Dead!
By Roger Frech, Senior Software Engineer
“Java is Dead”, “Java is Dying”, “Java is Obsolete” and other variations on the meme of Java mortality appear frequently on line in the IT “press”. These are click-bait, intended to draw your attention to a headline, or get some cheap SEO. For the more complex and nuanced truth about trends in Java usage – look beyond opinions for evidence.
VPN = Virtual Productivity is NONSTOP!
By James Cavazos, Senior Performance Test Engineer
In most tech companies, it has become commonplace to have VPN access to allow for working remotely. This can allow for greater productivity and flexibility for employees should they need to work from home or during business trips. It can also lead to some drawbacks. If you are not careful you could see a lot of your time-off spent doing work to the point that it feels like you never left the office. This can be especially difficult for workaholics and people with mindsets that can’t leave things unfinished.
A Practical Look at Go, Part 2
By Ken Walker Senior Software Engineer
In part 1 of this article, we looked at Go’s support for multiple threads and its approach to error handling. In this part, we’ll look at how Go approaches object orientation and how this would affect your daily routine.
A Practical Look at Go, Part 1
By Ken Walker Senior Software Engineer
About two years ago, I was working on a project written in the Go language. Go was originally developed by Google in 2007 for internal use, but was later released (open source) for general use. The project I was on was a large enterprise-wide service that collected large amounts of data (and did it well). This article introduces some of the interesting aspects of the language that might entice you to consider it for your own use, while pointing out a few things of which to be aware if you do.
Noting Special Events in Retrospectives, to Capture Sources of Technical Debt
By Paul Cooper, Senior Performance Test Engineer
A fundamental expectation for a high performing Agile team is to have clear requirements to begin building the product(s) with sprints and validating demos. The Agile approach supports the philosophy and the reality as long as the integrity of the requirements remain clear and well thought through. What happens when requirements run amok? Continue reading
Data Driven Testing – Separating Automation Code from Test Data
By Paul Cooper, Senior Performance Test Engineer
Test automation can be a costly time consuming endeavor. Often automation code and test data become entangled, leading to both fragile tests and fragile automation code. Once that happens, new tests will require programming to implement them. This helps us understand why testers now need coding skills. Design changes to the application, such as changing where or how a value is input, will also require updating the automation code and in turn may disrupt the test data.
Binding a Floating Point Property to a TextBox With a StringFormat in WPF
By Ken Walker Senior Software Engineer
Microsoft’s WPF bindings are a fine piece of technology. They are flexible and powerful, allowing changes to your objects’ properties to ripple through the rest of your application with a minimal amount of coding effort.
Continue reading
Locating DOM Elements for Functional E2E Tests Using Custom Attributes
by Larry Van Sickle, Senior Software Engineer
Protractor and Selenium are widely used tools for building functional end-to-end (e2e) automated tests. These tests execute a web-based application under test through a browser interface. The automated tests need to examine web page elements to determine whether their contents match expected results. They also need to operate on a webpage’s elements to drive the application. The tests need to click buttons, select from menus, and enter text in fields as part of the automated tests. A key problem and design decision is how the automated tests will locate elements in the DOM.