Software Engineering

Software Engineering

Using Data To Drive Your Development Process

Many software teams think of testing as a simple "smoke test" or perhaps an automated GO/NO GO for a release . In actual fact, even simple software test suites are a much richer data source. Simple time series of commit history, test results, and performance results, even for non-performance tests, can provide deeper insight for the release manager. This talk will discuss our experience at Solano Labs with a few of ...more »

Submitted by (@sfoster)

Voting

5 votes
5 up votes
0 down votes
In Review

Software Engineering

Automated Testing For The Web and Beyond

Much has been made of automated testing for web and Software as a Service products. This talk will discuss our experience at Solano Labs using automated testing to help web and SaaS vendors deliver high-quality software with confidence. Automated testing is replacing manual QA not only in the SaaS realm but also in more conservative parts of the software industry. Storage and networking vendors are starting to ask ...more »

Submitted by (@sfoster)

Voting

4 votes
4 up votes
0 down votes
In Review

Software Engineering

Scaling Continuous Integration: From Toy to Enterprise Backbone

This talk reviews the steps Infonova, a 300+ employee software company producing software for the telco world, went from the first efforts introducing a CI-tool for a single team to using the CI infrastructure for more than 30 (partly distributed) Scrum teams. While the initial installation was not really taken seriously by the developers, now the CI-infrastructure has become the backbone of the development department. ...more »

Submitted by (@stefanbrantner)

Voting

0 votes
0 up votes
0 down votes
In Review

Software Engineering

Drop the XP practices!

Automated testing, refactoring, continuous integration and pair programming are some of the most useful practices I find in my toolkit. However there are times when they just get in the way. In this short but controversial talk, we'll explore the value of each of these practices and find when they come unstuck. More importantly, you'll leave knowing when to make the most of them.

Submitted by (@patkua)

Voting

0 votes
1 up votes
1 down votes
In Review

Software Engineering

Scenario based testing- multiple browsers, devices, environments

A case-study on how Lovely Systems tied together existing open source tools to provide a solution which provides the stake holders of an agile software project a live view on the current implementation status of their system. The framework was developed in the course of a software project for a german enterprise customer. Built on top of Jenkins, Robotframework, Python and various other open-source components, the framework ...more »

Submitted by (@jodokbatlogg)

Voting

10 votes
10 up votes
0 down votes
Active

Software Engineering

Self-Experimentation for Continuous Improvement

Have you ever struggled to convince a team that your ideas have merit? How can you tell if the change you proposed at the last retrospective will actually pay off? How can we build a mindset of experimentation into team behavior? What if there were a powerful way to demonstrate through your own actions the legitimacy (or fallacy) of your ideas? Self experimentation offers us a way to test out our ideas and demonstrate ...more »

Submitted by (@tom.perry)

Voting

5 votes
5 up votes
0 down votes
Active

Software Engineering

Rapid Software Architecture Exploration

For agile teams who desire effective yet lean software engineering practices, Rapid Software Architecture Exploration is a set of structured, lightweight architecture design, discovery, and description practices designed to efficiently explore the design space and articulate a working solution. Unlike prevailing architecture-centric practices such as the Quality Attributes Workshop (QAW), Rapid Software Architecture ...more »

Submitted by (@michaelkeeling)

Voting

6 votes
6 up votes
0 down votes
Active

Software Engineering

Thinking about TDD: A Russian Doll, Full of Clockworks

Another take on Inside-Out/Outside-In thinking in test-driven development. Two simple, connected thought patterns, with examples, that helps you avoid serious but all too common mental pitfalls of different takes on test-driven development like TDD, BDD, ATDD. Too often both beginners and seasoned TDD-ers skip all the tests for the hard part of a piece of code. We find that the hard The Russian Doll pattern helps us think ...more »

Submitted by (@eriklundh)

Voting

4 votes
5 up votes
1 down votes
Active

Software Engineering

Sparse Testing for Quality and Flexibility

Come and discuss another take on how we can turn some currently tacit knowledge of the best TDD practitioners into a practice that reduces the suffering of many peoiple coming into TDD when they build real systems. Sparse testing: To radically reduce the state space we need to test just by a slightly different take on TDD. Wherever yous use an object or component wou write an “usage test” that act similar to the Observer ...more »

Submitted by (@eriklundh)

Voting

3 votes
3 up votes
0 down votes
In Review

Software Engineering

Measure and Manage Flow in Practice

Measure and Manage Flow is the third of the core principles of Kanban. It means that the members of the organisation are supposed to measure their progress and use the gathered information to improve their way of working. The most famous measurement tool for Kanban is the Cumulative Flow Diagram, but there are other usable approaches out there. During the last two years I tried out those different measurement approaches, ...more »

Submitted by (@zsoltfabok)

Voting

1 vote
2 up votes
1 down votes
In Review

Software Engineering

I broke the WIP Limit Twice, and I'm Still on the Team!

The Kanban method offers more than just visualizing your work and limiting the work in progress (WIP). Those are undoubtedly important principles, but there are other equally important principles and techniques that one can use with the Kanban Method. Among other things, there is the organisational perspective, the incremental and evolutionary change and the possibility to use tools and techniques from other areas such ...more »

Submitted by (@zsoltfabok)

Voting

1 vote
2 up votes
1 down votes
In Review

Software Engineering

How to Narrow Down What to Test

Nowadays testing legacy code, especially writing automatic test cases costs a lot. This looks like an extra expense in the short run, but saves a lot of trouble in the long run. However, not every organisation can afford to spend expensive coding time on testing that is considered having as no real value to the customer. Especially when we are talking about a large piece of untested legacy code. The best way to do ...more »

Submitted by (@zsoltfabok)

Voting

1 vote
3 up votes
2 down votes
Active