Spinning Code: DrupalCon Nashville Notes

Planet Drupal - 11. April 2018 - 6:50

Like last year I’m keeping an extremely rough setup of notes from DrupalCon as a repository of things I’m picking up and tracking of sessions that looked like they would be interested but that I couldn’t attend because I was in another session. I’ll clean then up a bit and add to them over time.

Thank you to everyone who is currently working really hard to make the event a success.

If you are kicking around con and want to meet up, contact me through here, Drupal.org, or Drupal Slack.

Monday I attended the Community Summit, and while I had lots of great discussions, I didn’t take a lot of notes. The biggest two things I noted were that Western New York DUG is doing interesting stuff with online meetings that might be worth checking out and emulating for the SC DUG. And that Mid-Camp keeps a list of all the various channels that have videos of Drupal Camp sessions.

DriesNote:

Roadmap:
The current roadmap looks pretty cool, assuming everything comes together as well as we all hope it will:

Announcing the new #Drupal8 Roadmap revealed by @Dries during today’s #DriesNote in #DrupalCon Nashville https://t.co/wKCQfvcbAr pic.twitter.com/mK5s4afe71

— DrupalCon Nashville (@DrupalConNA) April 10, 2018

Dries showed off some great stuff from the new demo site called Umami. Umami has been committed for 8.6, and we might be able to see it later in 8.5

Small correction: Umami demo is *already* in #Drupal 8.6 and we are hoping to even expose it in a later release of 8.5! #DrupalCon #driesnote

— webcsillag (@webchick) April 10, 2018

JS modernization and a new admin interface design are on their way, media library is part of that, but is likely a year out from being ready for prime-time.

Webchick summed this section of the talk nicely:

So rad to see the Out-of-the-Box and Layout initiatives being shown off together. Feels like #drupal 8 is really coming together for site builders and content authors! #driesnote #drupalcon

— webcsillag (@webchick) April 10, 2018

We are very over due for the needs of content creators, so it’s great to see meaningful headway on some of these processes.

Dries then moved on to start talking about values. It’s something he’s still not clearly fully comfortable doing, but it was good to see him try. The first public version of his attempt to define a set of values is up.

My read is that its well intended and has some ground to cover is it gets revised. I haven’t done a deep dive into its details yet, nor the response, but early reviews are mixed.

Frankly that Values statement leaves me a little cold. “Treating others with dignity and respect” !== “Creating a safe and inclusive community” #Driesnote #drupalcon

— Heather Rodriguez (@hrodrig) April 10, 2018

Although there was much less discussion today in hallways and informal chatting than I’d expected to here.

And there is definitely some ground to cover on issues that got us here in the first place:

Tech conf presenters who are white dudes, with slides of only images of white dudes, quotes only from white dudes

as a service

— Johanna Bates @ DrupalCon (@hanabel) April 10, 2018

(That’s not related to the DriesNote directly, something she ran into at later session but was on topic of my comments)

JavaScript and Accessibility: Don’t Blame the Language

https://events.drupal.org/nashville2018/sessions/javascript-and-accessibility-dont-blame-language

This was a really good session on accessibility with both a real world set of examples and realistic discussions of what’s hard and what happens when things pass tests but don’t get tested by humans.

Major take aways:

  • Modern tools support JS and it no longer gets in the way of accessibility. WCAG 1.0 said this was a problem 20 years ago, but that’s not the current best practice.
  • There are constraints to the work because of accessibility, but it they don’t have.
  • “There are times that I go to use an interactive calendar on the web and all I hear is 1, 2, 3, 4, 5, 6, 7, 8, 9, and so on to 30 or 31…with no indication that these are dates…just a mass of numbers in the middle of the page.”
  • We used to test sites by disabling CSS/JS. Now it makes more sense to try to navigate the site with a keyboard and see what happens. Remember that just because something is possible it doesn’t mean it’s obvious or good. This doesn’t get you to a great site, but allows you to pick off errors before someone finds them for you later.
  • When you tab to things, the visual affordances some designers hate can be put back in as a compromise for people using accessibility tools.
  • I need to spend more time with the iPhone voice over tool so I can test things better.
Things I didn’t go to in this window:
  • https://events.drupal.org/nashville2018/sessions/making-inclusion-happen-through-mentoring
  • https://events
  • .drupal.org/nashville2018/sessions/build-banging-sites-bpm-bricks-paragraphs-and-modifiers
  • https://events.drupal.org/nashville2018/sessions/big-changes-small-agencies
  • https://events.drupal.org/nashville2018/sessions/managing-your-most-important-resource-you
UX for Admin:

https://events.drupal.org/nashville2018/sessions/modernize-d8-admin-ux-and-accessibility-material-admin-theme

This was a really interesting session on the Material Admin theme, and what’s been needed to make it work.  It’s not perfect, and may or may not be ready for prime-time, but it looks like a great idea and show what we can do to make the admin much better.

Related projects:

  • https://www.drupal.org/project/material_admin
  • https://www.drupal.org/project/material_admin_support
  • https://www.drupal.org/project/type_style

Major take aways:

  • We’re behind, some of fixing that is easy, some of fixing that is hard.
  • When you’re UX is bad, people perceive things to be slow even if they aren’t. People think that material theme is faster even though it is demonstrably not.
  • Growth and survival of the project require us to have a better admin.
  • He’s trying to make sure add-ons for the theme/module are pretty standalone and just work. But theme’s can’t require modules which is silly.
  • Contenta uses Material by default on front and back because it provides decoupling well.
Skipped in this window:
  • https://events.drupal.org/nashville2018/sessions/take-images-to-next-level-drupal-8
  • https://events.drupal.org/nashville2018/sessions/web-accessibility-higher-education (Canceled )
  • https://events.drupal.org/nashville2018/sessions/drupal-core-auto-update-architecture
  • https://events.drupal.org/nashville2018/sessions/pdfs-drupal (overcrowded)
Salesforce BOF:

This BOF was a chance for Cornell to show off some great stuff they have been doing with Message Agency. They have done some cool stuff that shows the power for D8 and a good Salesforce integration.

@Cornell in the house at #DrupalConNA #Drupalcon2018 talking CRM (salesforce) & CMS integrations and best practices using both and interconnecting them at key points. pic.twitter.com/sH5nW9c73R

— Patrick Burns (@digitalburns) April 10, 2018

It should go without saying, but it needs saying too much:

A Salesforce is a CRM. Drupal is a CMS.

Use your tools for what they are best at.

The content in Drupal, actions recorded back into Salesforce.

Lessons:
1) Know strengths of each tool
2) Understand user needs
3) Determine how you will use each tool
4) Get the details right: SSO, Data Mapping, etc.

Drupal is much better at providing accessibility, including Form Assembly which is hard. The SF eco-system is mixed on the whole.

One option for multiple databases is https://www.snaplogic.com/ (apparently it is “capital intensive”).

So you have a Code of Conduct… now what?

https://events.drupal.org/nashville2018/sessions/so-you-have-code-conduct-now-what

This was a mini session that is worth watching if you’re unsure about the importance and value of having a code of conduct.  The hope had been to have a discussion about the importance of Drupal’s CoC, but everyone who attended largely agreed about the broad strokes of the major issues that have been discussed lately in the community.  We ended up talking more about how to broaden the discussion than about the CoC itself.

Skipped:

https://events.drupal.org/nashville2018/sessions/keeping-kittens-safe-while-altering-drupal-core

Handling a Big Year: ACLU.org in 2017

https://events.drupal.org/nashville2018/sessions/handling-big-year-acluorg-2017

This session was an interesting look at the impact on ACLU’s D6 (yes that’s right) advocacy site running on Pantheon.

Moved to Pantheon in 2013. And that move dealt with limits of their old hosting solution. Unfortunately some of my old-timey knowledge of why that had that solution was so old they couldn’t tell me much about how they had managed to make that move.

“Crazy things happen all the time”

After the their ED made a Rachel Maddow appearance on 11/16/16 they saw an 85x traffic spike. Tag1 was called in to help sort out what happened.

Traffic spiked to just over 500 requests per minute during the interview.

They found it was database bound, which was very common on D6, but still something they see frequently.

Found queries with 3 table join with no indexes on the base table. Able to go from 200,000 rows being scanned, down to 76. They were responding in real-time in crisis response mode.

After the wave passed, they called Pantheon to help build out environments for testing using multi-dev.

During the spikes that followed for the first travel ban, which were even larger they worked to reroute errors to Fastly, which served a PayPal fundraising link: at least the donations kept coming but that wasn’t good enough.

They needed a botnet to replicate the traffic. Tag1 used: Locust to create load tests, SaltStack to organize the bots, and EC2 to be the bots. They were failing at ~600 requests per minute and they were able to get to ~5,000 requests per minute. At that point the payment gateways were also starting to buckle, which isn’t a thing most people see.

The final wave they discussed came after the Net Neutrality lose, which peaked around 1,900 form submissions/min.

ACLU needed more logging, but didn’t want them logging personal information. Turned out the payment gateway’s CDN was detecting a DDOS and blocking them. See curl_log and curl_loadbalance. They also intentionally shift load from MySQL to Redis and PHP(?!?) because they knew Pantheon could scale that are far and as fast as needed to handle the waves, but MySQL was a limiting factor.

Skipped:
  • https://events.drupal.org/nashville2018/sessions/automate-your-automation
  • https://events.drupal.org/nashville2018/sessions/principles-content-layout
There is plenty left to come.

Agiledrop.com Blog: AGILEDROP: What got us here, won't get us there.

Planet Drupal - 11. April 2018 - 6:46
Day one at DrupalCon Nashville started with the traditional keynote by Drupal's founder Dries Buytaert. Dries talked about what is new and where are we heading. One of the main announcements was the Promote Drupal Initiative. The goal of this initiative is to start a promotional campaign that will enable to make Drupal known and loved by new decision makers. The same evening I happen to see a tweet from a formal active Drupal contributor that was questioning the director of Drupal. The tweet that got deleted very quickly said that we are compromising quality with marketing bulls**t. My first… READ MORE

Breitbandausbau: Landkreistag warnt vor digitaler Spaltung von Stadt und Land

heise online Newsticker - 11. April 2018 - 6:00
Beim Ausbau der digitalen Infrastruktur fühlen sich ländliche Gebiete abgehängt. Sie verlangen mehr Hilfen vom Bund. Auch über Wohnungsleerstand und knappe Finanzen wollen Landräte bei der Jahrestagung des Deutschen Landkreistags sprechen.

Drupal Association blog: We asked, you answered. DrupalCon North America Location Survey Results

Planet Drupal - 10. April 2018 - 22:17

Over the past few years, we’ve been listening to the community ask for explanation as to why we haven’t had any DrupalCon North America locations outside of the United States - after all it’s called DrupalCon North America, not DrupalCon U.S.A. This isn’t something we’ve taken lightly or ignored. DrupalCon North America is a major funding source for the Drupal Association, and in that regard, a major funding source of Drupal.org and the engineering work that keeps the code accessible and available for everyone.

We’ve looked at many North American cities over the years - a lot in the United States, but some outside the U.S. also. For our 2019 and 2020 location search we directly asked several cities in Canada to bid on this event, so that we could do financial and accomodation comparisons against U.S. options. I will give you the spoiler up front: 2019 and 2020 will not be in Canada or Mexico, they will be in the United States. The cities that bid were competitive, but in the end did not prevail due to things like dates overlapping with Passover and simply not being the most effective bid in comparison to the winners.

But with these cities in mind, and the voices of the community in our ears, we decided to go deeper and explore what a Canadian or Mexican DrupalCon would look like, based on survey feedback from the community and hard numbers from our history and bids. Here is that deeper look.

First, let me say that Drupal Association staff does not think solely about finances in making these decisions. We spend a lot of time getting to know the city, the vibe, the culture and the openness to a community that celebrates diversity and has a plethora of unique needs. It’s important to you, and it’s important to us.

Let’s also acknowledge that DrupalCon North America greatly underwrites the Drupal Association work and Drupal.org infrastructure to help keep the project going. So while money is not the only thing - it is very important.

So, let’s talk about finances. There are a lot of things that go into making a DrupalCon financially viable, and we did a pretty thorough job of outlining them all in our blog series last fall dedicated to the finances of DrupalCon Europe. I suggest you take a look at those, specifically the one on Solving The Financial Problem to get a good understanding on what it takes to make DrupalCon happen. A truncated look shows that there are three (3) main aspects and goals to DrupalCon finances:

  • Expenses: everything we have to spend to make it happen
    • Goal: produce show on a tight budget
  • Revenue, attendee tickets: how many people will show up
    • Goal: people show up
  • Revenue, sponsorship commitment: how much sponsors will spend to support the event
    • Goal: sponsorships have value and continue to support us
Expenses

In a look at expenses there are a vast array of things that we spend money on - from facilities and catering to program guides and paying the person who watches coat check while you’re sprinting on Friday. And overall, the proposals we’ve received from cities within the United States and outside of the United States have been fairly competitive for expenses directly related to the venue and infrastructure. That’s awesome!

There are some other indirect expenses we consider too like cost of hotel rooms, which can greatly affect whether people can afford to stay in the city, and generally Canadian cities - for example - tend to be a bit more expensive than some of our U.S. options. Other considerations include: whether the city is a airport hub for enough domestic and international flights to get people there easily; ease of setting up foreign bank accounts or legal business statuses in specific countries in order for us to operate there (including increased staff time to do this); cost of import/export for our production gear (this applies to sponsors as well). There are workarounds for some of these, and that's what we explore during an RFP process. Based on estimates, a DrupalCon outside the United States tends to pen out to be at least 10% more expensive than one within the United States - that’s around $100,000 - $150,000.

In general, the expenses section is a place where we can explore more work-arounds and potentially find a way to make a non-U.S. DrupalCon happen. However, because of DrupalCon team capacity during 2017 (the timeframe while we were contracting 2019 - 2020 cities) this is not something we could do for the immediately upcoming DrupalCons.

Revenue

As I mentioned above, revenue from DrupalCon North America is a driving force for the Drupal Association and Drupal.org. Ensuring attendee ticket sales and sponsorship revenue remain consistent from year to year (or grow) is extremely important to helping ensure our staff are funded and Drupal.org is kept running. In order to make certain that funding holds consistent and we’re able to keep Drupal.org healthy we need to keep DrupalCon North America profit margins around roughly 30-35% per event.

Here is where things start to fall apart for non-U.S. cities in the immediate future.

To better evaluate our current and potential revenue, we created 2 surveys and put them out to the public/community to participate.

Survey targets:

  • Past and potential attendees
  • Past and existing sponsors
Revenue, Attendee Ticket Sales

DrupalCon attendees are the main audience where we hear the cry for a DrupalCon outside of the United States. Individual ticket sales make up 62% of our event revenue.

Our survey to attendees had 1258 respondents. 92% of those people have attended DrupalCon North America in the past, and 99% have attended a DrupalCon somewhere in the world. So this sample represents people who are likely to attend in the future.

Since we’re talking about Revenue, it’s important to know who is paying for these people to attend. 79% of these attendees are funded by their employers. That’s a significant number and important to think about as we move into a business case for companies to attend DrupalCon.

Next, we followed up on that. “If your employer funds your trip to DrupalCon, are they willing to pay for you to travel outside the U.S.?” Of our 79% - 38% answered “No” (this number is adjusted from the chart percentages below because the question was “IF your employer pays”, and 120 people answered that they pay for themselves). That means, of our original sample size, now only 71% of attendees are still eligible to attend (22% self-funded + (62% of 79%) = roughly 71%).

Based on the responses, our projected revenue would decrease by roughly 29%.

Revenue, Sponsorships

Sponsors provide 38% of DrupalCon revenue, their sponsorships currently underwrite the cost of early bird tickets (that’s a whole other problem), and the event would simply not happen without them. They provide the foundation for the event in financing, they are the exhibit hall, and a large portion of our attendees are sponsor company employees. If sponsors don't come, we lose money and don't achieve a key purpose of our event: connecting new business decision makers with agency owners to grow adoption.

In our survey to them, we presented a hypothetical scenario in which DrupalCon takes place in Canada.

Our leading question for sponsors was “Do you do business in Canada?” and 70% of 44 responses said “No”. This doesn’t eliminate possibility, but it is the trend for the questions that followed.

We also asked “Would you sponsor a DrupalCon in Canada at same levels as you have in the past?” and only 39% of respondents answered “Yes”.

Of these sponsors, many wrote anecdotally that they simply could not support a business case for having an event in Canada.

To Sum it Up

While we’ve had advanced talks with Canadian cities, and two were finalists for 2019 and 2020 making it past initial RFP rounds, as of now we haven’t found solutions to enough of these issues to fit a DrupalCon North America within our required profit margin.

The numbers presented by the surveys would put profit margin for a DrupalCon North America outside the U.S. at an estimated 6% profit margin and would risk actually losing money for the Drupal Association. A situation and risk we cannot allow the Association to bear.

This is disappointing for many of us - and we know it is for many of you as well. We would love to see DrupalCon North America move beyond the U.S. borders, however it will not happen until at least 2021.

In between now and our next location RFP, we will continue to look at models that might make this possible. As we explore these challenges and talk more with sponsors and cities, we will share with the community any progress or new challenges as they become relevant. We appreciate your passion on this topic and understand the concerns with hosting DrupalCon in the United States for another two (2) years, especially based in our current climate of travel restraints in to the U.S. We wish it were not difficult for our community to come together.

We appreciate everyone who took the time to participate in our surveys and were honest about their desires, motivations and realities of their travel to and participation in DrupalCon. We're excited seeing many of you in Nashville this week, and hope many of you will join us in 2019 for DrupalCon Gedfyuikemndjfkioiujhtrj - sorry, something has happened to my keyboard. ¯\_(ツ)_/¯

_________________________

We invite you to share thoughts in the comments section below on how you think DrupalCon 2019 and 2020 can help provide more opportunity for community members outside the United States to participate in the event - either through direct attendance or through virtual participation of some kind. What are your ideas?

File attachments:  Business in Canada.png Employer Fund International Travel.png WhoFunds.png Would you Sponsor.png

Facebook: Zuckerberg löschte seine Nachrichten aus den Posteingängen der Empfänger

heise online Newsticker - 10. April 2018 - 18:30
Mark Zuckerberg und einige Führungskräfte von Facebook haben gesendete Nachrichten aus den privaten Nachrichteneingängen der Empfänger gelöscht. Nachdem das bekannt wurde, kündigte das Unternehmen nun diese Funktion für alle an.

Cubot X18 Plus: 6 Zoll, Android 8 und Dual-Kamera ab 120 Euro

heise online Newsticker - 10. April 2018 - 18:00
Das Cubot X18 Plus scheint ein vielversprechendes und vor allem günstiges Smartphone zu sein. In China-Shops ist ab 120 Euro, direkt in Deutschland für um die 200 Euro zu bekommen. Was das Gerät sonst noch drauf hat, erklärt TechStage im Test.

Dries Buytaert: Defining Drupal's values and principles

Planet Drupal - 10. April 2018 - 17:47

Since its founding, Drupal has grown a great deal, and today there are thousands of contributors and organizations that make up our community. Over the course of seventeen years, we have spent a great amount of time and effort scaling our community. As a result, Drupal has evolved into one of the largest open source projects in the world.

Today, the Drupal project serves as a role model to many other open source projects; from our governance and funding models, to how we work together globally with thousands of contributors, to our 3,000+ person conferences. However, the work required to scale our community is a continuous process.

Prompted by feedback from the Drupal community, scaling Drupal will be a key focus for me throughout 2018. I have heard a lot of great ideas about how we can scale our community, in addition to improving how we all work together. Today, I wanted to start by better establishing Drupal's values and principles, as it is at the core of everything we do.

Remarkably, after all these years, our values (what guides these behaviors) and our principles (our most important behaviors) are still primarily communicated through word of mouth.

In recent years, various market trends and challenging community events have inspired a variety of changes in the Drupal community. It's in times like these that we need to rely on our values and principles the most. However, that is very difficult to do when our values and principles aren't properly documented.

Over the course of the last five months, I have tried to capture our fundamental values and principles. Based on more than seventeen years of leading and growing the Drupal project, I tried to articulate what I know are "fundamental truths": the culture and behaviors members of our community uphold, how we optimize technical and non-technical decision making, and the attributes shared by successful contributors and leaders in the Drupal project.

Capturing our values and principles as accurately as I could was challenging work. I spent many hours writing, rewriting, and discarding them, and I consulted numerous people in the process. After a lot of consideration, I ended up with five value statements, supported by eleven detailed principles.

I shared both the values and the principles on Drupal.org as version 1.0-alpha. I labeled it alpha, because the principles and values aren't necessarily complete. While I have strong conviction in each of the Drupal principles and corresponding values, some of our values and principles are hard to capture in words, and by no means will I have described them perfectly. However, I arrived at a point where I wanted to share what I have drafted, open it up to the community for feedback, and move the draft forward more collaboratively.

While this may be the first time I've tried to articulate our values and principles in one document, many of these principles have guided the project for a very long time. If communicated well, these principles and values should inspire us to be our best selves, enable us to make good decisions fast, and guide us to work as one unified community.

I also believe this document is an important starting point and framework to help address additional (and potentially unidentified) needs. For example, some have asked for clearer principles about what behavior will and will not be tolerated in addition to defining community values surrounding justice and equity. I hope that this document lays the groundwork for that.

Throughout the writing process, I consulted the work of the Community Governance Group and the feedback that was collected in discussions with the community last fall. The 1.0-alpha version was also reviewed by the following people: Tiffany Farriss, George DeMet, Megan Sanicki, Adam Goodman, Gigi Anderson, Mark Winberry, Angie Byron, ASH Heath, Steve Francia, Rachel Lawson, Helena McCabe, Adam Bergstein, Paul Johnson, Michael Anello, Donna Benjamin, Neil Drumm, Fatima Khalid, Sally Young, Daniel Wehner and Ryan Szrama. I'd like to thank everyone for their input.

As a next step, I invite you to provide feedback. The best way to provide feedback is in the issue queue of the Drupal governance project, but there will also be opportunities to provide feedback at upcoming Drupal events, including DrupalCon Nashville.

UKW-Frequenzen: Abschaltung vorerst abgewendet, aber Streit geht weiter

heise online Newsticker - 10. April 2018 - 17:30
Der Betreiber einer Sendeinfrastruktur hatte im Streit um Geld mit der Zwangsabschaltung mehrerer UKW-Sender gedroht. Nun hat sich das Unternehmen offenbar mit zwei Netzbetreibern auf einen Weiterbetrieb geeinigt - jedoch vorerst nur bis zur Jahresmitte.

Convertible-PC HP ZBook Studio x360 G5: 4K-Display mit 600 Lumen

heise online Newsticker - 10. April 2018 - 17:00
HP frischt die mobilen Workstations seiner ZBook-Serie auf. Der Convertible-PC Studio x360 G5 erhält ein 4K-Display, das mit 600 Lumen strahlt. Das größte Modell ZBook 17 kann bis zu 10 TByte Daten speichern.

150 Jahre TU München: Rückbesinnung der Technik auf die Gesellschaft gefordert

heise online Newsticker - 10. April 2018 - 17:00
Den Menschen muss die Angst vor den technischen Entwicklungen genommen werden, findet der Präsident der TU München. In der Forschung muss die Technik enger mit der Sozial- und Humanwissenschaft verbunden werden.

Acro Media: Automated Drupal Code Testing: What, Why, and When To Do It

Planet Drupal - 10. April 2018 - 16:45

Automated testing is like flossing your teeth: you know you should do it, you might even tell people you do it, but chances are you don't do it nearly as often or as consistently as you ought to. Maybe you only run one automated test. On five percent of your code. Sometimes.

Manual testing vs automated testing

Manual testing—where a real live person clicks around and verifies that the code does everything it's supposed to do—has its uses. But for large-scale projects, or in cases where you need to test the same code repeatedly, automated testing can be both more cost-effective and more fruitful. You know how your eye can look at the same spelling error six times without seeing it? Automated testing can catch issues like that. It's great for rote, boring tasks that humans gloss over.

In test-driven development, you actually build the tests first and then write the code that fulfills those tests. But you don't necessarily have to do automated testing that way. Tests can be written afterwards. Sometimes it's old code that gets automated tests built for it, for instance.

Writing the test probably takes more time than it takes to initially test it. But then it's done, and you can re-run the test any time you make any change to that site. Even if you don't change anything near that code, you can run the test anyways and catch those instances where you're like, "I'm sure it won't break that"…but it does.

Drupal maintainers try to be really strict about the automated tests. Since lots of people use the modules, and lots of people contribute to them, you have all these different people submitting code. Having a good test suite can really improve your confidence in a module. If each submission comes with new tests that you can run and verify, you can be far more confident in the quality of that code.

Time savings

Say you do 10 hours of manual testing for each release. If, on the other hand, you spend 10 hours writing automated tests for each release, then for release #2, you're actually doing 20 hours of testing, and for release #3 you're doing 30 hours of testing. You're only putting in 10 man hours each time, but your test suite keeps growing, and the scope of what you're testing increases exponentially because you can rerun the same tests each time.

Why is automated testing such a hard sell?

Going back to the flossing example: why don't you floss? It takes 60 seconds. But you only really get the benefits if you do it all the time.

More to the point: not doing it takes time to become bad. Skipping automated testing on your first release is maybe not a big deal. Your code base is small, it's probably only doing a couple things, so manual testing is very feasible. But as the project grows and gets more complex, manual testing becomes increasingly unwieldy, and then you get to a point where you think, we're too far into this to add automated testing now.

But the truth is you can start at any point. It's never too late to start proactively doing things that will benefit your site.

What prevents people from getting started?

Usually the thing that stymies people is that they're not set up for automated testing: they don't have a continuous integration environment or a nice testing environment to run the tests on. Or maybe they've neglected it for so long that the regular tests don't work anymore; they write their first test and they have all these other problems because they've let things languish, so they give up.

What is continuous integration, you ask? It means every time you do a change and you push it out, it attempts to integrate it in with the whole project. It will deploy it to a server, it will compile the code if necessary, it will run code standards and automated tests and so on. When you have that stuff all set up to run automatically, you just make the code, push it to your version control, and forget about it. If something goes south, it'll send you an email saying this didn't pass. Otherwise, you don't have to think about it again.

How much of your code should be covered by automated testing?

You kind of want to be in that 95% range, although it's true that you can have parts that aren't easily testable. You can cover a lot of code, but you might still be missing use cases. Maybe you test taxes, and you test discounts, but you don't test taxes and discounts together. So technically you have full code coverage, but you're not using them in combination. So code coverage is a nice metric, but it doesn't tell the whole story.

TLDR: Automated testing is like flossing. You should really do it.

More from Acro Media Chat with us

If you'd like to talk about adding automated testing to your Drupal Commerce website, or if you just want to to discuss how Drupal Commerce fits into your ecommerce solution, give us a shout. We're happy to chat.

Fabrik der Zukunft immer unabhängiger vom Standort

heise online Newsticker - 10. April 2018 - 16:30
Noch vernetzter, noch intelligenter: Die Fabrik der Zukunft wird smart. Doch damit könnte der Standort Deutschland an Bedeutung verlieren. Hannover-Messe-Chef Köckler fordert daher die "optimale Infrastruktur" für die digitale Zukunft.

Natur von romantisch bis skurril: Die Bilder der Woche (KW 14)

heise online Newsticker - 10. April 2018 - 16:00
Die Naturfotografie kennt viele spannende Facetten. Einige davon präsentieren wir hier mit den prämierten Bildern dieser Woche aus der Online-Galerie von c't Fotografie.

roomify.us: Tutorial: showing BEE reservations on an event calendar

Planet Drupal - 10. April 2018 - 15:55
BEE makes it easy to quickly implement all kinds of booking & reservation use cases. We've created a new video that walks you through setting up an event calendar displaying BEE reservations.

Was war. Was wird. Vom Unrecht des Vergessens und anderen deutschen Befindlichkeiten

heise online Newsticker - 10. April 2018 - 15:30
Sie wollten vergessen, die rechtschaffenen Deutschen im Wirtschaftswunderland, und das ließen die 68er nicht zu, sagt Hal Faber 50 Jahre später. Nun sind die nächsten neuen Deutschen (wieder?) da und krakeelen zurück in die Zukunft.

Elektromobilität: Umweltministerin will Kaufprämie von 7000 Euro für E-Lieferwagen

heise online Newsticker - 10. April 2018 - 15:00
Mit einer nahezu verdoppelten Elektroauto-Prämie will Svenja Schulze E-Lieferwagen für Logistiker und Handwerker lohnenswert machen. Das soll die Luftqualität in Städten verbessern, denn eine rechtliche Handhabe für Diesel-Nachrüstungen gebe es nicht.

Studie: Roboter bedrohen Jobs in Deutschland stärker als in anderen Industrienationen

heise online Newsticker - 10. April 2018 - 14:30
Die Entwicklung von Robotern und Software kann in etwa 20 Jahren jeden fünften Arbeitnehmer in Deutschland ersetzen, besagt eine OECD-Studie. Deutschland ist stärker betroffen als die meisten anderen Mitgliedsstaaten.

Facebook-Datenskandal: Beraterfirma AggregateIQ ebenfalls suspendiert

heise online Newsticker - 10. April 2018 - 14:00
Nach Bekanntwerden des Skandals um Cambridge Analytica hat Facebook ein weiteres Unternehmen ausgesperrt. AggregateIQ war an der Kampagne der Brexit-Befürworter beteiligt und soll Verbindung zu CA gehabt haben.

Diesel-Skandal: EU-Kommission soll europaweite Sammelklagen vorbereiten

heise online Newsticker - 10. April 2018 - 14:00
Laut einem Zeitungsbericht will die EU-Kommission einen Vorstoß für europaweite Sammelklagen unternehmen. Damit könnten Verbände Schadenersatzklagen gegen Autohersteller einreichen. Das ginge weit über ein Vorhaben der Bundesregierung hinaus.