Test Case | Expected outcome | Pass / Fail | Tester’s Comments | ||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Login to Lawmaker as an OPC user
| Dashboard displayed (or last tab associated with the project you last viewed) Top-right menu on the dashboard shows that I am logged in with my username Able to see projects that have been created by OPC users Able to see projects that have a published Bill or Act in them from other organisations Unable to see projects created by other organisations that do not have a published Bill in them |
| ||||||||||||||||||||||||||||||||||||||||||
2 | Create a New Bill Project Select UK Public Bill > Government Bill
| A new project is created, visible only to users in the same organisation as the current user It appears on the main Dashboard Project tab opens for the new document Editor opens in a new tab showing an empty template document |
| ||||||||||||||||||||||||||||||||||||||||||
3 | Check and edit document information for the bill Bill using the Document Information panel in the Editor
| Document information displays correctlyis updated in the main editor window Able to edit: Title, Session, Year, Rubric Details are changed or populated in the main editor pane after the change is made in the Doc Info panel |
| ||||||||||||||||||||||||||||||||||||||||||
4 | Create some content in the Editor using the CCA Inserting provisions and other elements
| CCA is displayed Creates a realistic looking BillCCA is displayed Able to creates a realistic looking Bill within the Editor Structure view (left-hand side of the Editor window) is updated in line with new elements created in the Editor |
| ||||||||||||||||||||||||||||||||||||||||||
5 | Insert 2 two or more schedules | The "SCHEDULES" heading will appear before the first schedule When inserting three or more schedules: If “Auto-renumbering” is OFF then schedules will not be renumbered If “Auto renumbering” is ON then schedules will still not be renumbered (feels counter intuitive but is technically by design if not intention) |
| ||||||||||||||||||||||||||||||||||||||||||
6 | Press Ctrl+S or click on the Save button | A progress bar appears and progresses to 100% A message is displayed saying ‘Document Saved’ On the project tab, the version last modified is the same as the time it was saved |
| ||||||||||||||||||||||||||||||||||||||||||
7 | Renumber the whole Bill | All provisions will be renumbered sequentially including all their descendants.
|
| ||||||||||||||||||||||||||||||||||||||||||
8 | Add one or more J-Refs to Sections or Schedules (v13) Managing J-refs | J-Refs are display displayed in the Editor in Red And the Each J-ref will be is also visible in the structure view |
| ||||||||||||||||||||||||||||||||||||||||||
9 | Create cross reference(s) to sections that contain J-refs. Click Tag X-refs | You can toggle on and off to display the J-ref in cross-references (Tools > Show/hide J-refs in cross references) |
| 10 | Turn on Track Changes Delete one or more elements / Insert element(s) and move element(s) | Inserted and deleted elements are display in the editor and blue (insert) or red (deleted)
| Able to copy a reference out of the structure view Able to paste a reference in another part of the document Able toggle on and off to display the J-ref in cross-references (from the toolbar: Tools > Show/hide J-refs in cross references) and these J-refs are then shown alongside the pasted cross references |
| |||||||||||||||||||||||||||||||||||||
10 | Turn on Tracked Changes Delete one or more elements, insert one or more elements, and move one or more elements | Inserted and deleted elements are display in the editor and blue (insert) or red (deleted) |
| ||||||||||||||||||||||||||||||||||||||||||
11 | Insert a Table of Contents | Table of Contents is inserted at the start of the document "Front cover" appears in the Structure View |
| ||||||||||||||||||||||||||||||||||||||||||
12 | Generate a PDF Ensure:
| PDF is generated in separate tab Table of Contents is included Tracked changes are displayed in red for deleted text; blue for inserted text J-Refs are shown in margins J-Refs are shown next to x-refs No snapshot is visible on the Project tab |
| ||||||||||||||||||||||||||||||||||||||||||
13 | Make some more small changes in the Editor and then close the Editor using the Close button in the top-left | Prompted to Save changes |
| ||||||||||||||||||||||||||||||||||||||||||
14 | Duplicate a document Duplicating a document version
| New folder created with a duplicated version inside it |
| ||||||||||||||||||||||||||||||||||||||||||
15 | Open a document version in the Editor Click the fold button in the toolbar, then use the Structure View to expand a particular provision
| The Editor will jump to the selected provision, and unfold it, showing the content |
| ||||||||||||||||||||||||||||||||||||||||||
16 | Create a new working version
| A new working version is created which appears on the 'Project' tab under the appropriate folder heading. Clicking on it to open it in the Editor will reveal an empty new document, allowing you to start drafting Able to save and close the new working version |
| ||||||||||||||||||||||||||||||||||||||||||
17 | Edit Portion of a document Opening and editing a portion of document
| The selected subset of provisions is opened in the Editor The highest level provisions e.g. sections, regulations or Parts, will have their numbers locked so that when you renumber the document, they do not get automatically updated |
| ||||||||||||||||||||||||||||||||||||||||||
18 | Close the Editor and Finalise the document Tick all options in the Finalise modal
| All provisions in the document, including provisions in quoted structures, are renumbered All existing cross references in the document are updated accordingly, including those within quoted structures If ‘Insert Front Cover’ is selected: any existing front cover is replaced, including the Table of Contents If ‘Insert Table of Contents’ is selected: any existing table of contents is replaced, but other parts of the front cover are left as they are |
| ||||||||||||||||||||||||||||||||||||||||||
19 | Move a version to a new folder | Selected version is moved to another existing folder or to the newly created folder specified in the modal |
| ||||||||||||||||||||||||||||||||||||||||||
20 | Share a version with the House of Commons | A Significant version of the Bill is created on the project tab This version is also visible to HoC users This version is not visible to users in other organisations |
| ||||||||||||||||||||||||||||||||||||||||||
21 | Login as a HoC user and navigate to the project created by OPC in previous steps | Dashboard displayed (or last tab associated with the project you last viewed) Top-right menu on the dashboard shows that I am logged in with my username Able to see projects that have been created by HoC users Able to see projects that have a published Bill or Act in them from other organisations Unable to see projects created by other organisations that do not have a published Bill in them In the bill project created by OPC in previous steps, a significant version of the Bill is visible on the project tab with the same name as the original working version |
| ||||||||||||||||||||||||||||||||||||||||||
22 | Make a working copy of the significant version
| A working version of the Bill is created, duplicating the content of the significant version The new working version appears in the selected folder or newly created folder (with the name specified in the modal) Able to open and edit the new working version |
| ||||||||||||||||||||||||||||||||||||||||||
23 | Mark sections/schedule paragraphs/subsections/schedule sub-paragraphs in a UK Bill as a "money provision" so that it (and all its descendants) is rendered in italics in the Editor and PDF | Able to set provisions as money provisions Money provisions should appear italic in the Editor and in the generated PDF Descendants of those provisions also display in italics |
| ||||||||||||||||||||||||||||||||||||||||||
24 | Update document information for the new working version Example details to add/change: Session: 58/1, Bill year: 2021, Bill number: Bill 221, version rubric: "As introduced", printed by: "House of Commons" | Bill title and version rubric are updated in the editor, corresponding to the changes made in the Doc Info panel On the Dashboard showing all projects, Bill number and session are updated |
| ||||||||||||||||||||||||||||||||||||||||||
25 | Manage proposers and supporters on a Bill in the Editor
| Able to add and remove proposers and supporters Able to change the order of names by dragging and dropping in a different order |
| 11 | Insert a Table of Contents | ||||||||||||||||||||||||||||||||||||||||
26 | Add Back cover to the Bill | Back cover will be inserted at the end of the Bill in the Editor The back cover shows the Bill is being introduced by the proposer The back cover shows the Bill is being supported by the supporters The back cover shows the introduction date |
| ||||||||||||||||||||||||||||||||||||||||||
27 | Re-insert the Back cover after changing proposers and supporters and updating the printed date | Back cover is reinserted and replaces the existing one Proposers/supporters names are updated The printed date is updated |
| 12 | Generate PDF Ensure:
| PDF is generated in separate tab Table of Contents is included Tracked changes are displayed in red for deleted text; blue for inserted text J-Refs are shown in margins J-Refs are shown with x-refs No snapshot is visible on the Project tab PDF Version is named using the text entered in the ‘Version description’ field
| |||||||||||||||||||||||||||||||||||||||
28 | Insert a Front cover | Front cover shows the Bill title in the editor Any existing Table of Contents is replaced with an up-to-date Table of Contents |
| 13 | Delete the table of contents | ||||||||||||||||||||||||||||||||||||||||
29 | Generate a PDF of the Bill with changes applied, line numbering, and footers; include a footer note; ensure ‘Record snapshot version’ is ticked Prompted to Save changes
| Table of contents is removed |
| 14 | Close the Editor |
| PDF opens in new tab The PDF contains line numbering and footers Footer note text is correct Output PDF shows changes applied |
| 15 | Duplicate a document | |||||||||||||||||||||||||||||||||||
30 | Publish a significant version of the generated PDF Publishing a Bill document version
Documents and folders on the Project Tab New folder created with a duplicated version inside it
| Significant version created on the right-hand side of the Project tab Significant version visible to users in other organisations Copy of the Bill is accessible through the PDR API | Open a document version in the Editor Use the fold button in the toolbar, then use the Structure View to expand a particular provision
The Editor will jump to the selected provision, and unfold it
| 16 |
| ||||||||||||||||||||||||||||||||||||||||
31 | Create an ‘as amended’ folder and version by duplicating the published version
| New working version with the specified name in the specified folder is created |
| 17 | Create a new working version
| ||||||||||||||||||||||||||||||||||||||||
32 | Open the newly created ‘as amended’ version in the Editor and change some Document Information: Change the ‘printed' date Update the document rubric to ‘as amended in Committee’ Re-insert the front and back covers Save and close the Editor | Able to update the document information from the Editor Text shown in the main Editor pane updates accordingly Text on the front and back covers is updated accordingly |
| ||||||||||||||||||||||||||||||||||||||||||
1833 | Edit Portion of a document Opening and editing a portion of document
| The selected subset of provisions is opened in the Editor AND the section or schedule nums are locked or grouping level nums (for body only - not in schedules)Generate a PDF and publish the ‘as amended’ version
| Significant version created on the right-hand side of the Project tab Significant version visible to users in other organisations Copy of the Bill is accessible through the PDR API |
| 19 | Close the Editor and Finalise the document
| Assuming you selected all options: All provisions in the document, including provisions in quoted structures, are renumbered All existing cross references in the document and update them accordingly - including those within quoted structures If Insert Front Cover is selected: any existing front cover is replaced, including the Table of Contents If you select Insert Table of Contents: any table of contents if there is one but will leave other parts of the front cover as they are. | ||||||||||||||||||||||||||||||||||||||
34 | Generate the House Bill
| Able to generate a House Bill First page of the PDF shows the year, bill short title and long title with appropriate styling |
| 20 | Move a version to a new folder | Selected version is moved to another existing folder or to the newly created folder specified in the modal |
| ||||||||||||||||||||||||||||||||||||||
21 | Share a version with the House of Commons | A Significant version of the Bill is created on the project tab This version is also visible to HoC users This version is not visible to users in other organisations | 35 | Share a new copy with the House of Lords Sharing a document with another organisation
| Significant version created on the right-hand side of the Project Tab Significant version label will start with the word ‘Shared’ |
| |||||||||||||||||||||||||||||||||||||||
2236 | Login as a HoC user Dashboard displayed (or last tab associated with the project you last viewed) Top-right menu on the dashboard shows that I am logged in with my username Able to see projects that have been created by HoC users Able to see projects that have a published Bill or Act in them from other organisations Unable to see projects created by other organisations that do not have a published Bill in themHoL user, navigate to the same project, and Duplicate a version of this shared copy to create a new working version | Able to create a new working version in the folder you specify in the modal Version label has the name you specified in the modal |
| 23 | Open the project created by OPC in previous steps |
| |||||||||||||||||||||||||||||||||||||||
37 | Update the Document information from the Actions menu on the Project Tab to make this the “as brought from the Commons” version Specify a Bill number, e.g. HL Bill 29 Specify a ‘brought from’ date Specify that it is printed by the House of Lords | All changes are possible in the modal Clicking Update works as expected When opening the document in the Editor, new document information is visible (you may have to re-insert the front and back covers - see next step) |
| 24 | Make a working copy of the significant version
| A working version of the Bill is created, duplicating the content of the significant version The new working version appears in the selected folder or newly created folder (with the name specified in the modal) Able to open and edit the new working version
| |||||||||||||||||||||||||||||||||||||||
38 | Open this version in the Editor and reinsert the front and back covers | Able to reinsert the front and back covers Back cover shows correct version rubric and brought from/printed by dates |
| 25 | Update document information for the new working version Example details to add/change: Session: 58/1, Bill year: 2021, Bill number: Bill 221, version rubric: "As introduced", printed by: "House of Commons" | Bill title and version rubric are updated in the editor, corresponding to the changes made in the Doc Info panel On the Dashboard showing all projects, Bill number and session are updated | |||||||||||||||||||||||||||||||||||||||
39 | Generate a PDF of this version and then create a Significant version Generating and viewing a PDF Publishing a Bill document version | Able to generate PDF Able to select Publish version from the Actions menu next to the PDF snapshot Warning modal is displayed On clicking Publish, a new significant version is created on the right-hand side of the Project Tab Version is accessible through the PDR API with the correct House and docType values |
| 26 | Manage proposers and supporters on a Bill in the Editor | Able to add and remove proposers and supporters Able to change the order of names by dragging and dropping in a different order |
| 27 | Add Back cover to the Bill | ||||||||||||||||||||||||||||||||||||
40 | Create an ‘as amended’ folder by duplicating a version
| New working version with the specified name in the specified folder is created |
| ||||||||||||||||||||||||||||||||||||||||||
2841 | Re-insert the Back cover after changing proposers and supporters and updating the printed date | Back cover is reinserted and replaces the existing one And proposers/supporters names are updated And the printed date is updated |
| 29 | Insert a Front cover | Front cover shows the Bill title in the editor Any existing Table of Contents is replaced with an up-to-date Table of ContentsOpen the newly created ‘as amended’ version in the editor and change some Document Information: Change the ‘printed' date Update the document rubric Re-insert the front and back covers | Text shown in the main Editor pane update accordingly Text on the front and back covers is updated accordingly |
| |||||||||||||||||||||||||||||||||||||
42 | Create an Act version of the Bill Converting a UK Bill into an Act
| Fail | 30 | Generate a PDF of the Bill with line numbering and footers; include a footer note
| PDF opens in new tab And the PDF contains line numbering and footers Footer note text is correct |
| 31 | Publish a significant version of the generated PDF | Significant version created on the right-hand side of the Project tab Significant version visible to users in other organisations Copy of the Bill accessible through the PDR API
| New working version created containing an Act version of the bill Act title is correct Text on the cover and preface change accordingly in the main Editor pane |
| ||||||||||||||||||||||||||||||||||
43 | Generate a PDF of this Act version; ensure ‘Record snapshot’ is ticked | PDF snapshot is generated |
| 32 | Create an ‘as amended’ folder by duplicating a version Expand | | |||||||||||||||||||||||||||||||||||||||
44 | Submit the Act to TNA From the Actions menu next to a version on the Project tab, select Duplicate versionCreate a new folder (“Committee”) and give the version a label (“as amended”) Tick the option which removes page/line numbers New working version with the specified name in the specified folder is createdthe PDF snapshot, select ‘Submit to TNA’ | Warning is displayed, with Submit and Cancel buttons On clicking Submit, a new Significant version is created The Act is available through the PDR API |
| 33 | Open the newly created ‘as amended’ version in the editor and change some Document Information: Change the ‘printed' date Update the document rubric Re-insert the front and back covers | ||||||||||||||||||||||||||||||||||||||||
45 | Download a ZIP of the Act and resolve dates in the XML | Able to download a ZIP of the Act ZIP contains the Act XML, PDF, and any images |
| ||||||||||||||||||||||||||||||||||||||||||
46 | |||||||||||||||||||||||||||||||||||||||||||||
3447 | |||||||||||||||||||||||||||||||||||||||||||||
48 |
Page Comparison
General
Content
Integrations