Abstract
In a world overwhelmed by constant data creation and manipulation, where privacy is becoming a real concern, topics like data usage control, accountability, provenance, protected sharing of resources and trustworthiness of knowledge sources are becoming main topics of discussion among communities of interest. In this paper enhancements are proposed for an existing framework that tackles some of the afore mentioned issues namely data provenance, usage control and accountability. Such proposals consist of providing means for publishing resources in a private manner hereby making websites behave like meshes of hyperlinked resources from different domains, not only for resources publicly published but also for the ones protected by access policies. © 2014, Society, Privacy and the Semantic Web Policy and Technology.

Abstract
Today's software feature user interface (UI) patterns. Those patterns describe generic solutions for common recurrent problems. However, to the best of our knowledge, there is no specific testing methodology that is particularly suited for testing those patterns providing generic testing solutions that can be reused after minor configurations in order to test slightly different implementations. Pattern-Based Graphical User Interface Testing (PBGT) is a recent methodology that aims at systematizing and automating the GUI testing process, by sampling the input space using "UI Test Patterns" that express generic solutions to test common recurrent GUI's behaviour. This paper describes the development process of PARADIGM, a domain specific language (DSL) to be used in the context of PBGT and empirically evaluates PARADIGM to assess its diminished modeling efforts, usefulness, graphical power, and acceptability.

Abstract
Graphical user interfaces (GUIs) have become popular as they appear in everydays' software. GUIs have become an ideal way of interacting with computer programs, making the software friendlier to its users. GUIs have grown, and so has the usage of UI Patterns featured in GUIs. UI Patterns are recurring solutions to solve common GUI design problems. We developed the notion of UI Test Patterns that, are able to test different implementations of UI Patterns. Therefore, we created a new methodology called Pattern-Based GUI Testing (PBGT) that aims at systematizing and automating the GUI testing process. PBGT samples the input space using UI Test Patterns, which provide a reusable and configurable test strategy, in order to test a GUI that was implemented using a set of UI Patterns. In this paper we present three UI Test Patterns: Login, Master/Detail and Sort. Copyright © 2014 ACM.

Abstract
A great deal of effort in model-based testing is related to the creation of the model. In addition, the model itself, while a powerful tool of abstraction, can have conceptual errors, introduced by the tester. These problems can be reduced by generating those models automatically. This paper presents a dynamic reverse engineering approach that aims to extract part of the model of an existing web application through the identification of User Interface (UI) patterns. This reverse engineering approach explores automatically any web application, records information related to the interaction, analyses the gathered information, tokenizes it, and infers the existing UI patterns via syntactical analysing. After being complemented with additional information and validated, the model extracted is the input for the Pattern-Based Graphical User Interface Testing (PBGT) approach for testing existing web application under analysis.

Abstract

Abstract
Currently, software tends to assume increasingly critical roles in our society so assuring its quality becomes ever more crucial. There are several tools and processes of software testing to help increase quality in virtually any type of software. One example is the so called Model-Based Testing (MBT) tools, that generate test cases from models. However, most of these tools have a configuration phase, where test input data is provided manually by the tester, which influences the quality of the test suite generated. By adding coverage analysis to MBT tools it is possible to give feedback and help the tester to define the configuration data needed to achieve the most valuable test suite as possible. This paper presents a tool, PARADIGM-COV, that produces coverage information both over the PARADIGM model elements (to assess if input data is adequate to cover the test goals and assess if preconditions are achievable), and during test case execution (to identify the parts of the model/code that were actually exercised).