Get Advanced Testing of Systems-of-Systems, Volume 2 - Practical Aspects 1st Edition Bernard Homes Free All Chapters
Get Advanced Testing of Systems-of-Systems, Volume 2 - Practical Aspects 1st Edition Bernard Homes Free All Chapters
Get Advanced Testing of Systems-of-Systems, Volume 2 - Practical Aspects 1st Edition Bernard Homes Free All Chapters
com
https://ebookmeta.com/product/advanced-testing-of-
systems-of-systems-volume-2-practical-aspects-1st-
edition-bernard-homes/
OR CLICK BUTTON
DOWLOAD EBOOK
https://ebookmeta.com/product/advanced-testing-of-systems-of-
systems-volume-1-theoretical-aspects-1st-edition-bernard-homes/
https://ebookmeta.com/product/advanced-computing-and-systems-for-
security-volume-13-1st-edition-rituparna-chaki/
https://ebookmeta.com/product/practical-aspects-of-vaccine-
development-the-practical-aspects-1st-edition-parag-kolhe-editor/
https://ebookmeta.com/product/intelligent-sustainable-systems-
selected-papers-of-worlds4-2021-volume-2-1st-edition-atulya-k-
nagar/
Advanced Computing and Systems for Security Volume 14
Lecture Notes in Networks and Systems 242 1st Edition
Rituparna Chaki (Editor)
https://ebookmeta.com/product/advanced-computing-and-systems-for-
security-volume-14-lecture-notes-in-networks-and-systems-242-1st-
edition-rituparna-chaki-editor/
https://ebookmeta.com/product/legal-aspects-of-autonomous-
systems-a-comparative-approach-1st-edition-dario-moura-vicente/
https://ebookmeta.com/product/radiation-detection-systems-
medical-imaging-industrial-testing-and-security-applications-
devices-circuits-and-systems-2nd-edition/
https://ebookmeta.com/product/applications-of-big-data-and-
artificial-intelligence-in-smart-energy-systems-volume-2-1st-
edition-neelu-nagpal-editor/
https://ebookmeta.com/product/advanced-dynamics-modeling-duality-
and-control-of-robotic-systems-1st-edition-edward-y-l-gu/
Advanced Testing of Systems-of-Systems 2
Advanced Testing of
Systems-of-Systems 2
Practical Aspects
Bernard Homès
First published 2022 in Great Britain and the United States by ISTE Ltd and John Wiley & Sons, Inc.
Apart from any fair dealing for the purposes of research or private study, or criticism or review, as
permitted under the Copyright, Designs and Patents Act 1988, this publication may only be reproduced,
stored or transmitted, in any form or by any means, with the prior permission in writing of the publishers,
or in the case of reprographic reproduction in accordance with the terms and licenses issued by the
CLA. Enquiries concerning reproduction outside these terms should be sent to the publishers at the
undermentioned address:
www.iste.co.uk www.wiley.com
Any opinions, findings, and conclusions or recommendations expressed in this material are those of the
author(s), contributor(s) or editor(s) and do not necessarily reflect the views of ISTE Group.
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
10.8.3. Prevalidation regression tests, sanity checks and smoke tests . . . . . . . 179
10.8.4. What to automate? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
10.8.5. Test frameworks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
10.8.6. E2E test cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
10.8.7. Automated test case maintenance or not? . . . . . . . . . . . . . . . . . . 184
10.9. Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
10.9.1. Automated reporting for the test manager . . . . . . . . . . . . . . . . . . 186
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
I would also like to thank the many managers and colleagues I had the privilege
of meeting during my career. Some, too few, understood that quality is really
everyone’s business. We will lay a modest shroud over the others.
Testing Qualification Board), CFTL (Comité Français des Tests Logiciels, the
French Software Testing committee) and GASQ (Global Association for Software
Quality). I also dedicate these books to you, the reader, so that you can improve your
testing competencies.
Preface
Implementation
August 2022
1
deadlines, the scope initially considered increases, the level of quality of input data –
requirements, components to be tested, interfaces – is often of lower quality than
expected and the number of faults or anomalies is greater than anticipated. All of
these are under tighter budgetary and calendar constraints because, even if the
developments take longer than expected, the production launch date is rarely
postponed.
The methodologies offered by ITIL, PRINCE2, CMMI, etc. bring together a set
of good practices that can be adapted – or not – to our system-of-systems project.
CMMI, for example, does not have test-specific elements (only IVV), and it may be
necessary to supplement CMMI with test-specific tasks and actions as offered by
TMM and TMMI.
The execution of the tests is carried out in different test environments according
to the test levels envisaged. It will therefore be necessary to ensure the availability
of environments for each level.
4 Advanced Testing of Systems-of-Systems 2
Test environments, as well as their data and the applications they interface with
must be properly synchronized with each other. This implies an up-to-date definition
of the versions of each system making up the system-of-systems and of the
interfaces and messages exchanged between them.
It is obvious that the input test data of a test case and the expected data at the
output of a test case are necessary, and it is also important to have a set of other data
that will be used for testing:
– data related to the users who will run the tests (e.g. authorization level,
hierarchical level, organization to which they are attached, etc.);
– information related to the test data used (e.g. technical characteristics,
composition, functionalities present, etc.) and which are grouped in legacy systems
interfaced with the system-of-systems under test;
– historical information allowing us to make proposals based on this historical
information (e.g. purchase suggestions based on previous purchases);
– information based on geographical positioning (e.g. GPS position), supply
times and consumption volumes to anticipate stock replenishment needs (e.g. need
to fill the fuel tank according to the way to drive and consume fuel, making it
possible to offer – depending on the route and GPS information – one or more
service stations nearby);
– etc.
Test Project Management 5
The creation and provision of quality test data is necessary before any test
campaign. Designing and updating this data, ensuring that it is consistent, is
extremely important because it must – as far as possible – simulate the reality of the
exchanges and information of each of the systems of the system-of-systems to be
tested. We will therefore need to generate data from monitoring systems (from
sensors, via IoT systems) and ensure that their production respects the expected
constraints (e.g. every n seconds, in order to identify connection losses or deviations
from nominal operating ranges).
Test data should be realistic and consistent over time. That is, they must either
simulate a reference period and each of the campaigns must ensure that the systems
have modified their reference date (e.g. use a fixed range of hours and reset systems
at the beginning of this range) or be consistent with the time of execution of the test
campaign. This last solution requires generating the test data during the execution of
the test campaign, in order to verify the consistency of the data with respect to the
expected (e.g. identification of duplicate messages, sequencing of messages, etc.)
and therefore the proper functioning of the system-of-systems as a whole.
Development and construction projects are associated with often strict delivery
dates and schedules. The impact of a late delivery of a component generates
cascading effects impacting the delivery of the system and the system-of-systems.
Timely delivery, with the expected features and the desired level of quality, is
therefore very important. In some systems-of-systems, the completeness of the
functionalities and their level of quality are often more important than the respect of
the delivery date. In others, respecting the schedule is crucial in order to meet
imperatives (e.g. launch window for a rocket aiming for another planet).
This involves close collaboration between test manager and project managers in
charge of the design and production of components, products or systems to be
6 Advanced Testing of Systems-of-Systems 2
tested, as well as managers in charge of test environments and the supply of test
data.
In the context of Agile and Lean methods, any delay in deliveries and any
non-compliance with schedules is a “loss of value” and should be eliminated. It is
however important to note that the principles of agility propose that it is the
development teams that define the scope of the functionalities to be delivered at each
iteration.
Depending on the test levels, environments will include more and more
components, products and systems that will need to coordinate to represent test
environments representative of real life. Each environment includes one or more
systems, components, products, as well as interfaces, ETLs and communication
equipment (wired, wireless, satellite, optical networks, etc.) of increasing
complexity. The design of these various environments quickly becomes a full-time
job, especially since it is necessary to ensure that all the versions of all the software
are correctly synchronized and that all the data, files, contents of databases and
interfaces are synchronized and validated in order to allow the correct execution of
the tests on this environment.
Testing activities can start effectively and efficiently as soon as all their
prerequisites are present. Otherwise, the activities will have to stop and then start
again when the missing prerequisite is provided, etc. This generates significant
waste of time, not to mention everyone’s frustration. Before starting any test task,
we must make sure that all the prerequisites are present, or at the very least that they
will arrive on time with the desired level of quality. Among the prerequisites, we
have among others the requirements, the environment, the datasets, the component
to be tested, the test cases with the expected data, as well as the testers, the tools and
procedures for managing tests and anomalies, the KPIs and metrics allowing the
reporting of the progress of the tests, etc.
Test Project Management 7
One solution to ensure the presence of the prerequisites is to set up a TRR (Test
Readiness Review) milestone, a review of the start of the tests. The purpose of this
milestone is to verify – depending on the test level and the types of test – whether or
not the prerequisites are present. If prerequisites are missing, it is up to the project
managers to decide whether or not to launch the test activity, taking into account the
identified risks.
In Agile methods, such a review can be informal and only apply to one user story
at a time, with the acronym DOR for definition of ready.
The delivery of test datasets (TDS) is not limited to the provision of files or
databases with information usable by the component, product or system. This also
includes – for the applications, components, products or systems with which the
component, product or system under test interacts – a check of the consistency and
synchronization of the data with each other. It will be necessary to ensure that the
interfaces are correctly described, defined and implemented.
The design of coherent and complete datasets is a difficult task requiring a good
knowledge of the entire information system and the interfaces between the
component, product or system under test on the one hand and all the other systems
of the test environment on the other hand. Some components, products or systems
may be missing and replaced by “stubs” that will simulate the missing elements. In
this case, it is necessary to manage these “stubs” with the same rigor as if they were
real components (e.g. evolution of versions, data, etc.).
A Go-NoGo meeting is used to analyze the risks associated with moving to the
next step in a process of designing and deploying a component, product, system or
system-of-systems, and to decide whether to proceed to the next step.
In an Agile environment, the concept of Go-NoGo and TRB is detailed under the
concept of DOD (definition of done) for each of the design actions.
Another aspect to consider is the need for test automation and (1) the continued
increase in the number of tests to be executed, which will mean increasing test
execution time as well as (2) the need to ensure that the test classes in the software
(case of TDD and BDD) are correctly removed from the versions used in integration
tests and in system tests.
According to Kim et al. (2016), in companies like Amazon and Google, the
majority of teams practice continuous delivery and some practice continuous
deployment. There is wide variation in how to perform continuous deployment.
Monitoring test projects requires monitoring the progress of each of the test
activities for each of the systems of the system-of-systems, as well as on each of the
test environments of each of the test levels of each of these systems. It is therefore
important that the progress information of each test level is aggregated and
summarized for each system and that the test progress information of each system is
aggregated at the system-of-systems level. This involves defining the elements that
must be measured (the progress), against which benchmark they must be measured
(the reference) and identifying the impacts (dependencies) that this can generate.
Reporting of similar indicators from each of the systems will facilitate
understanding. Automated information feedback will facilitate information retrieval.
10 Advanced Testing of Systems-of-Systems 2
Systems-of-systems projects are subject to more risk than other systems in that
they may inherit upstream-level risks and a process’s tolerance for risk may vary by
organization and the delivered product. In Figure 1.1, we can identify that the more
we advance in the design and production of components by the various
organizations, the risks will be added and the impact for organizations with a low
risk tolerance will be more strongly impacted than others.
In Figure 1.2, we can identify that an organization will be impacted by all the
risks it can inherit from upstream organizations and that it will impose risks on all
downstream organizations.
can impact the final delivery of the component, product or system, or even the
system-of-systems.
– Side effects may appear on other components, so it will be necessary to retest
all components each time a component update is delivered. This solution can be
limited to the components interacting directly with the modified component(s) or
extend to the entire system-of-systems, and it is recommended to automate it.
– The interfaces between components may not be developed simultaneously and
therefore that the tests of these interfaces may be delayed.
It is not possible to envisage retesting all the combinations of data and actions of
the components of a level of a system-of-systems; this would generate a workload
disproportionate to the expected benefits. One solution is to verify that the design
and test processes have been correctly carried out, that the proofs of execution are
available and that the test activities – static and dynamic – have correctly covered
the objectives. These verification activities are the responsibility of the quality
assurance teams and are mainly based on available evidence (paper documentation,
execution logs, anomaly dashboards, etc.).
relationships with each other, others and to the outside. This information is grouped
into what NASA calls CRM (Crew Resource Management). Developed in the
1970s–1980s, CRM is a mature discipline that applies to complex projects and is
ideal for decision-making processes in project management.
It is essential to:
– recognize the existence of a problem;
– define what the problem is;
– identify probable solutions;
– take the appropriate actions to implement a solution.
If CRM is mainly used where human error can have devastating effects, it is
important to take into account the lessons that CRM can bring us in the
implementation of decision-making processes. Contrary to a usual vision, people
with responsibilities (managers and decision-makers) or with the most experience
are sometimes blinded by their vision of a solution and do not take into account
alternative solutions. Among the points to keep in mind is communication between
the different members of the team, mutual respect – which will entail listening to the
information provided – and then measuring the results of the solutions implemented
in order to ensure their effectiveness. Team members can all communicate important
information that will help the project succeed.
The specialization of the members of the project team, the confidence that we
have in their skills and the confidence that they have in their experience, the
management methods and the constraints – contractual or otherwise – mean that the
decision-making method and the decisions made can be negatively impacted in the
absence of this CRM technique. This CRM technique has been successfully
implemented in aeronautics and space, and its lessons should be used successfully in
complex projects.
2
Testing Process
These processes will all be involved to some degree in the testing processes.
Indeed, the test processes will decline the requirements, whether or not they are
defined in documents describing the conformity needs, and the way in which these
requirements will be demonstrated (type of IADT proofs), will split the types of
demonstration according to the levels test and integration (system, subsystem,
sub-subsystem, component, etc.) and static types (Analysis and Inspection for static
checks during design) or dynamic (demonstration and tests during the levels of
integration and testing of subsystems, systems and systems-of-systems). Similarly,
the activities of the test process will report information and progress metrics to
project management (CMMI PMC for Project Monitoring and Control process) and
will be impacted by the decisions descending from this management.
The processes described in this chapter apply to a test level and should be
repeated on each of the test levels, for each piece of software or containing software.
Any modification in the interfaces and/or the performance of a component
interacting with the component(s) under test will involve an analysis of the impacts
and, if necessary, an adaptation of the test activities (including about the test) and
evidence to be provided to show the conformity of the component (or system,
subsystem, equipment or software) to its requirements. Each test level should
coordinate with the other levels to limit the execution of tests on the same
requirements.
16 Advanced Testing of Systems-of-Systems 2
An additional process can be defined: the review process, which can be carried
out several times on a test level, on the one hand, on the input deliverables, and on
the other hand, on the deliverables produced by each of the processes of the level.
Review activities can occur within each defined test process.
The proposed test processes are applicable regardless of the development mode
(Agile or sequential). In the case of an Agile development mode, the testing
processes must be repeated for each sprint and for each level of integration in a
system-of-systems.
The processes must complement each other and – even if they may partially
overlap – it must be ensured that the processes are completed successfully.
2.1. Organization
Objectives:
– develop and manage organizational needs, in accordance with the company’s
test policy and the test strategies of higher levels;
– define the players at the level, their responsibilities and organizations;
– define deliverables and milestones;
– define quality targets (SLA, KPi, maximum failure rate, etc.);
– ensure that the objectives of the test strategy are addressed;
– define a standard RACI matrix.
Actor(s):
– CPI (R+A), CPU/CPO (I), developers (C+I);
– experienced “test manager” having a pilot role of the test project (R).
Prerequisites/inputs:
– calendar and budgetary constraints defined for the level;
– actors and subcontractors envisaged or selected;
– repository of lessons learned from previous projects.
Deliverables/outputs:
– organization of level tests;
– high-level WBS with the main tasks to be carried out;
18 Advanced Testing of Systems-of-Systems 2
Entry criteria:
– beginning of the organization phase.
Exit criteria:
– approved organizational document (ideally a reduced number of pages).
Indicators:
1) efficiency: writing effort;
2) coverage: traceability to the quality characteristics identified in the project test
strategy.
Points of attention:
– ensure that the actors and meeting points (milestones and level of reporting)
are well defined.
2.2. Planning
Objective:
– plan test activities for the project, level, iteration or sprint considering existing
issues, risk levels, constraints and objectives for testing;
– define the tasks (durations, objectives, incoming and outgoing, responsibilities,
etc.) and sequencing;
– define the exit criteria (desired quality level) for the level;
– identify the prerequisites, resources (environment, personnel, tools, etc.)
necessary;
– define measurement indicators and frequencies, as well as reporting.
Actor(s):
– CPI (R+A), CPU/CPO (I), developers (C+I);
– experienced testers “test manager”, having a role of manager of the test
project (R);
– testers (C+I).
Testing Process 19
Prerequisites/inputs:
– information on the volume, workload and deadlines of the project;
– information on available environments and interfaces;
– objectives and scope of testing activities.
Objective:
– plan test activities for the project or level, iteration or sprint considering
existing status, risk levels, constraints and objectives for testing;
– define the tasks (durations, objectives, incoming and outgoing, responsibilities,
etc.) and sequencing;
– define the exit criteria (desired quality level) for the level;
– identify prerequisites, resources (environment, personnel, tools, etc.)
necessary;
– define measurement indicators and frequencies, as well as reporting.
Actor(s):
– CPI (R+A), CPU/CPO (I), developers (C+I);
– experienced testers “test manager”, having a role of manager of the test project
(R);
– testers (C+I).
Prerequisites/inputs:
– REAL and project WBS defined in the investigation phase;
– lessons learned from previous projects (repository of lessons learned).
Deliverables/outputs:
– master test plan, level test plan(s);
– level WBS (or TBS for Test Breakdown Structure), detailing – for the
applicable test level(s) – the tasks to be performed;
– initial definition of test environments.
20 Advanced Testing of Systems-of-Systems 2
Entry criteria:
– start of the investigation phase.
Exit criteria:
– test plan approved, all sections of the test plan template are completed.
Indicators:
1) efficiency: writing effort vs. completeness and size of the deliverables
provided;
2) coverage: coverage of the quality characteristics selected in the project Test
Strategy.
Points of attention:
– ensure that test data (for interface tests, environment settings, etc.) will be well
defined and provided in a timely manner;
– collect lessons learned from previous projects.
Deliverables/outputs:
– master test plan, level test plan(s);
– level WBS, detailing – for the test level(s) – the tasks to be performed;
– detailed Gantt of test projects – each level – with dependencies;
– initial definition of test environments.
Entry criteria:
– start of the investigation phase.
Exit criteria:
– approved test plan, all sections of the applicable test plan template are
completed.
Indicators:
1) efficiency: writing effort;
2) coverage: coverage of the quality characteristics selected in the project’s test
strategy.
Testing Process 21
Points of attention:
– ensure that test data (for interface testing, environment settings, etc.) will be
well defined and provided in a timely manner.
Objective:
– throughout the project: adapt the test plan, processes and actions, based on the
hazards and indicators reported by the test activities, so as to enable the project to
achieve its objectives;
– identify changes in risks, implement mitigation actions;
– provide periodic reporting to the CoPil and the CoSuiv;
– escalate issues if needed.
Actor(s):
– CPI (A+I), CPU/CPO (I), developers (I);
– test manager with a test project manager role (R);
– testers (C+I) [provide indicators];
– CoPil CoNext (I).
Prerequisites/inputs:
– risk analysis, level WBS, project and level test plan.
Deliverables/outputs:
– periodic indicators and reporting for the CoPil and CoSuiv;
– updated risk analysis;
– modification of the test plan and/or activities to allow the achievement of the
“project” objectives.
Entry criteria:
– project WBS, level WBS.
Exit criteria:
– end of the project, including end of the software warranty period.
22 Advanced Testing of Systems-of-Systems 2
Indicators:
– dependent on testing activities.
2.4. Analyze
Objective:
– analyze the repository of information (requirements, user stories, etc. usable
for testing) to identify the test conditions to be covered and the test techniques to be
used. A risk or requirement can be covered by more than one test condition. A test
condition is something – a behavior or a combination of conditions – that may be
interesting or useful to test.
Actor(s):
– testers, test analysts, technical test analysts.
Prerequisites/inputs:
– initial definition of test environments;
– requirements and user stories (depending on the development method);
– acceptance criteria for (if available);
– analysis of prioritized project risks;
– level test plan with the characteristics to be covered, the level test environment.
Deliverables/outputs:
– detailed definition of the level test environment;
– test file;
– prioritized test conditions;
– requirements/risks traceability matrix – test conditions.
Entry criteria:
– validated and prioritized requirements;
– risk analysis.
Exit criteria:
– each requirement is covered by the required number of test conditions
(depending on the RPN of the requirement).
Another random document with
no related content on Scribd:
conceipt of Cynthia, (Phœbe and Cynthia being both names of
Diana.) So in the person of Prince Arthure I sette forth magnificence
in particular, which vertue for that (according to Aristotle and the rest)
it is the perfection of all the rest, and conteineth in it them all,
therefore in the whole course I mention the deedes of Arthure
applyable to that vertue, which I write of in that booke. But of the xii.
other vertues, I make xii. other knights the patrones, for the more
variety of the history: Of which these three bookes contayn three,
The first of the knight of the Redcrosse, in whome I expresse
Holynes: The seconde of Sir Guyon, in whome I sette forth
Temperaunce; The third of Britomartis a Lady knight, in whome I
picture Chastity. But because the beginning of the whole worke
seemeth abrupte and as depending vpon other antecedents, it needs
that ye know the occasion of these three knights seuerall
aduentures. For the Methode of a Poet historical is not such, as of
an Historiographer. For an Historiographer discourseth of offayres
orderly as they were donne, accounting as well the times as the
actions, but a Poet thrusteth into the middest, euen where it most
concerneth him, and there recoursing to the thinges forepaste, and
diuining of thinges to come, maketh a pleasing Analysis of all. The
beginning therefore of my history, if it were to be told by an
Historiographer should be the twelfth booke, which is the last, where
I deuise that the Faery Queene kept her Annuall feaste xii. dayes,
vppon which xii. seuerall dayes, the occasions of the xii. seuerall
aduentures hapned, which being vndertaken by xii. seuerall knights,
are in these xii books seuerally handled and discoursed. The first
was this. In the beginning of the feast, there presented him selfe a
tall clownishe younge man, who falling before the Queen of Faries
desired a boone (as the manner then was) which during that feast
she might not refuse: which was that hee might haue the
atchieuement of any adventure, which during that feaste should
happen, that being graunted, he rested him on the floore, vnfitte
through[638] his rusticity for a better place. Soone after entred a faire
Ladye in mourning weedes, riding on a white Asse, with a dwarfe
behind her leading a warlike steed, that bore the Armes of a knight,
and his speare in the dwarfes hand. Shee falling before the Queene
of Faeries, complayned that her father and mother an ancient King
and Queene, had bene by an huge dragon many years shut up in a
brasen Castle, who thence suffred them not to yssew: and therefore
besought the Faery Queene to assygne her some one of her knights
to take on him that exployt. Presently that clownish person
vpstarting, desired that aduenture: whereat the Queene much
wondering, and the Lady much gainesaying, yet he earnestly
importuned his desire. In the end the Lady told him that vnlesse that
armour which she brought, would serue him (that is the armour of a
Christian man specified by Saint Paul v. Ephes.) that he could not
succeed in that enterprise, which being forthwith put vpon him with
dewe furnitures thereunto, he seemed the goodliest man in al that
company, and was well liked of the Lady. And eftesoones taking on
him knighthood, and mounting on that straunge Courser, he went
forth with her on that aduenture: where beginneth the first booke, vz.
The second day ther came in a Palmer bearing an Infant with bloody
hands, whose Parents he complained to haue bene slayn by an
Enchaunteresse called Acrasia: and therfore craued of the Faery
Queene, to appoint him some knight, to performe that aduenture,
which being assigned to Sir Guyon, he presently went forth with that
same Palmer: which is the beginning of the second booke and the
whole subiect thereof. The third day there came in, a Groome who
complained before the Faery Queene, that a vile Enchaunter called
Busirane had in hand a most faire Lady called Amoretta, whom he
kept in most grieuous torment, because she would not yield him the
pleasure of her body. Whereupon Sir Scudamour the louer of that
Lady presently tooke on him that aduenture. But being vnable to
performe it by reason of the hard Enchauntments, after long sorrow,
in the end met with Britomartis, who succoured him, and reskewed
his loue.
But by occasion hereof, many other aduentures are intermedled, but
rather as Accidents, then intendments. As the loue of Britomart, the
ouerthrow of Marinell, the misery of Florimell, the vertuousnes of
Belphœbe, the lasciuiousnes of Hellenora, and many the like.
Thus much Sir, I haue briefly ouerronne to direct your understanding
to the wel-head of the History, that from thence gathering the whole
intention of the conceit, ye may as in a handfull gripe al the
discourse, which otherwise may happily seeme tedious and
confused. So humbly crauing the continuaunce of your honorable
fauour towards me, and th’ eternall establishment of your happines, I
humbly take leaue.
23. Ianuary. 1589.
Yours most humbly affectionate.
Ed. Spenser.
FOOTNOTES:
[635] A Letter, &c.] Om. 1596 Bodl.
[636] l. 16 by accidents 1590
[637] l. 16 ezpresse 1590
[638] l. 43 through 1590
COMMENDATORY VERSES
¶ A Vision vpon this conceipt of the Faery
Queene.
Me thought I saw the graue, where Laura lay,
Within that Temple, where the vestall flame
Was wont to burne, and passing by that way,
To see that buried dust of liuing fame,
Whose tombe faire loue, and fairer vertue kept,
All suddenly I saw the Faery Queene:
At whose approch the soule of Petrarke wept,
And from thenceforth those graces were not seene.
For they this Queene attended, in whose steed
Obliuion laid him downe on Lauras herse:
Hereat the hardest stones were seene to bleed,
And grones of buried ghostes the heauens did perse.
Where Homers spright did tremble all for griefe,
And curst th’accesse of that celestiall theife.
W. R.
Hobynoll.
R. S.
W. L.
Ignoto.
FOOTNOTES:
[639] Fayre Thamis. &c.] This poem and those that follow are
omitted in 1596 Bodl.
[640] l. 17 dew. 1590
[641] l. 30 this 1590
DEDICATORY SONNETS
To the right honourable Sir Christopher Hatton,
Lord high Chauncelor of England. &c.
Those prudent heads, that with theire counsels wise
Whylom the Pillours of th’earth did sustaine,
And taught ambitious Rome to tyrannise,
And in the neck of all the world to rayne,
Oft from those graue affaires were wont abstaine,
With the sweet Lady Muses for to play:
So Ennius the elder Africane,
So Maro oft did Cæsars cares allay.
So you great Lord, that with your counsell sway
The burdeine of this kingdom mightily,
With like delightes sometimes may eke delay,
The[642] rugged brow of carefull Policy:
And to these ydle rymes lend litle space,
Which for their titles sake may find more grace.
E. S.
E. S.
E. S.
To the most renowmed and valiant Lord, the Lord
Grey of Wilton, knight of the Noble order of the
Garter, &c.
Most Noble Lord the pillor of my life,
And Patrone of my Muses pupillage,
Through whose large bountie poured on me rife,
In the first season of my feeble age,
I now doe liue, bound yours by vassalage:
Sith nothing euer may redeeme, nor reaue
Out of your endlesse debt so sure a gage,
Vouchsafe in worth this small guift to receaue,
Which in your noble hands for pledge I leaue,
Of all the rest, that I am tyde t’account:
Rude rymes, the which a rustick Muse did weaue
In sauadge soyle, far from Parnasso mount,
And roughly wrought in an vnlearned Loome:
The which vouchsafe dear Lord your fauorable doome.
E. S.
E. S.
E. S.
E. S.
E. S.
To all the gratious and beautifull Ladies in the
Court.
The Chian Peincter, when he was requirde
To pourtraict Venus in her perfect hew,
To make his worke more absolute, desird
Of all the fairest Maides to haue the vew.
Much more me needs to draw the semblant trew,
Of beauties Queene, the worlds sole wonderment,
To sharpe my sence with sundry beauties vew,
And steale from each some part of ornament.
If all the world to seeke I ouerwent,
A fairer crew yet no where could I see,
Then that braue court doth to mine eie present,
That the worlds pride seemes gathered there to bee.
Of each a part I stole by cunning thefte:
Forgiue it me faire Dames, sith lesse ye haue not lefte.
E. S.
FOOTNOTES:
[642] l. 12 The] he 1590
[643] l. 33 furtheraunce, 1590
[644] l. 5 Emperesse, 1590
[645] l. 8 Souerain 1590
FINIS.