diff --git a/blazar_dashboard/api/client.py b/blazar_dashboard/api/client.py
index 21e5cb8..9378a43 100644
--- a/blazar_dashboard/api/client.py
+++ b/blazar_dashboard/api/client.py
@@ -97,7 +97,7 @@ def blazarclient(request):
 def lease_list(request):
     """List the leases."""
     leases = blazarclient(request).lease.list()
-    return [Lease(l) for l in leases]
+    return [Lease(lease) for lease in leases]
 
 
 def lease_get(request, lease_id):
diff --git a/test-requirements.txt b/test-requirements.txt
index 6b97fd6..3770d8d 100644
--- a/test-requirements.txt
+++ b/test-requirements.txt
@@ -1,19 +1,8 @@
-# The order of packages is significant, because pip processes them in the order
-# of appearance. Changing the order has an impact on the overall integration
-# process, which may cause wedges in the gate later.
-# Order matters to the pip dependency resolver, so sorting this file
-# changes how packages are installed.  New dependencies should be
-# added in alphabetical order, however, some dependencies may need to
-# be installed in a specific order.
-#
-# Hacking should appear first in case something else depends on pep8
-hacking>=3.0.1,<3.1.0 # Apache-2.0
-#
-coverage!=4.4,>=4.0 # Apache-2.0
-nodeenv>=0.9.4 # BSD
-pytest>=5.3.5 # MIT
-testtools>=2.2.0 # MIT
-
 # bandit is not included in upper-constraints, so we need to pin it here to a
 # known working version
 bandit==1.6.2 # Apache-2.0
+coverage!=4.4,>=4.0 # Apache-2.0
+hacking>=7.0.0,<7.1.0 # Apache-2.0
+nodeenv>=0.9.4 # BSD
+pytest>=5.3.5 # MIT
+testtools>=2.2.0 # MIT