* Update Archeion.js
* Update CiteULike.js
* Rewrite National Library of Australia (new catalog).js
* Update Code4Lib Journal.js
* Update jmlr.js
* Update Journal of Electronic Publishing.js
* Update Max Planck Institute for the History of Science Virtual Laboratory Library.js
* Update FreePatentsOnline.js
* Delete KOBV.js old portal
See http://vs13.kobv.de/V/?func=file&file_name=kobv-news#
for announcement of coming shutdown and link to new
portal.
* Rewrite Musee du Louvre.js
* Rewrite National Bureau of Economic Research.js
translator.setHandler("itemDone", function (obj, item) {
//the DC doesn't distinguish between personal and institutional authors - get them from the page and parse
var authors =ZU.xpath(doc, '//div[@id="archivalDescriptionArea"]//div[@class="field"]/h3[contains(text(), "Name of creator")]/following-sibling::div/a');
for (var i inauthors) {
for (let i=0; i<authors.length; i++) {
//remove location (in parentheses) from creators, since it often contains a comma that messes with author parsing
if (!item.creators[i].firstName) item.creators[i].fieldMode=1;
}
//The Archive gets mapped to the relations tag - we want its name, not the description in archeion
for (var i initem.seeAlso) {
for (let i=0; i<item.seeAlso.length; i++) {
if (item.seeAlso[i].indexOf("http://") ==-1) {
item.archive=item.seeAlso[i];
}
}
item.seeAlso= [];
//the RDF translator doesn't get the full identifier - get it from the page
var loc =ZU.xpathText(doc, '//section[@id="titleAndStatementOfResponsibilityArea"]//div[@class="field"]/h3[contains(text(), "Reference code")]/following-sibling::div');
Z.debug(loc)
//Z.debug(loc)
item.archiveLocation= loc;
item.libraryCatalog="Archeion - MemoryBC - Aberta on Record";
if (item.extra) item.notes.push(item.extra);
@@ -79,39 +119,15 @@ function scrape(doc, url) {
translator.getTranslatorObject(function(trans) {
trans.defaultUnknownType='book';
trans.doImport();
});
});
});
}
functiondoWeb(doc, url) {
if (detectWeb(doc, url) =="multiple") {
var articles =newArray();
var items =newObject();
var titles =ZU.xpath(doc, '//div[contains(@class, "search-results")]/h2/a|//div[contains(@class, "search-result")]/p[@class="title"]/a');
for (var i in titles) {
items[titles[i].href] = titles[i].textContent;
}
Zotero.selectItems(items, function (items) {
if (!items) {
returntrue;
}
for (var i in items) {
articles.push(i);
}
Zotero.Utilities.processDocuments(articles, scrape, function () {
"title":"Automatic test generation: a use case driven approach",
"creators": [
{
"lastName":"Nebut",
@@ -87,35 +123,48 @@ var testCases = [
"creatorType":"author"
}
],
"date":"March 2006",
"DOI":"10.1109/tse.2006.22",
"ISSN":"0098-5589",
"abstractNote":"Use cases are believed to be a good basis for system testing. Yet, to automate the test generation process, there is a large gap to bridge between high-level use cases and concrete test cases. We propose a new approach for automating the generation of system test scenarios in the context of object-oriented embedded software, taking into account traceability problems between high-level views and concrete test case execution. Starting from a formalization of the requirements based on use cases extended with contracts, we automatically build a transition system from which we synthesize test cases. Our objective is to cover the system in terms of statement coverage with those generated tests: an empirical evaluation of our approach is given based on this objective and several case studies. We briefly discuss the experimental deployment of our approach in the field at Thales Airborne Systems.",
"issue":"3",
"libraryCatalog":"CiteULike",
"pages":"140-155",
"publicationTitle":"IEEE Transactions on Software Engineering",
"shortTitle":"Automatic test generation",
"url":"http://dx.doi.org/10.1109/tse.2006.22",
"volume":"32",
"attachments": [],
"tags": [
{
"tag":"automation"
},
{
"tag":"test"
},
{
"tag":"test_case_generation"
},
{
"tag":"testing"
},
{
"tag":"use_case"
}
],
"notes": [
{
"note":"<p>This paper introduces a new approach to automatically generating test cases from requirements which are described by use cases and contracts. With the aid of sequence diagrams, test scenarios can be generated from test objectives. The authors also provide a simulator to correct requirements by doing simulation and model checking. When applying the approach to real life cases, requirement formalization still poses great challenges to business analysts.</p>"
}
],
"tags": [
"automation",
"test",
"test_case_generation",
"testing",
"use_case"
],
"seeAlso": [],
"attachments": [],
"title":"Automatic test generation: a use case driven approach",
"publicationTitle":"IEEE Transactions on Software Engineering",
"volume":"32",
"issue":"3",
"pages":"140-155",
"ISSN":"0098-5589",
"abstractNote":"Use cases are believed to be a good basis for system testing. Yet, to automate the test generation process, there is a large gap to bridge between high-level use cases and concrete test cases. We propose a new approach for automating the generation of system test scenarios in the context of object-oriented embedded software, taking into account traceability problems between high-level views and concrete test case execution. Starting from a formalization of the requirements based on use cases extended with contracts, we automatically build a transition system from which we synthesize test cases. Our objective is to cover the system in terms of statement coverage with those generated tests: an empirical evaluation of our approach is given based on this objective and several case studies. We briefly discuss the experimental deployment of our approach in the field at Thales Airborne Systems.",
0 comments on commit
5bb111a