Testing in Agent Oriented Methodologies

Espino, Mailyn Moreno; Pavón, Juán; Rosete, Alejandro

doi:10.1007/978-3-642-02481-8_20

Cited by 10 publications

(6 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Role is defined as a capability enabler that exposes to the agent that plays it a set of actions. The V-model [8] represented in figure 1 shows the development and its corresponding role based testing activity. The left branch of the V represents the specification flow, and the right branch represents the role oriented testing flow.…”

Section: B Testing In Aose Methodologiesmentioning

confidence: 99%

Agent Oriented Software Testing – Role Oriented approach

Sivakumar¹,

Vivekanandan²

2012

IJACSA

View full text Add to dashboard Cite

Abstract-Several Agent Oriented Software Engineering (AOSE) methodologies were proposed to build open, heterogeneous and complex internet based systems. AOSE methodologies offer different conceptual frameworks, notations and techniques, thereby provide a platform to make the system abstract, generalize, dynamic and autonomous. Lifecycle coverage is one of the important criteria for evaluating an AOSE methodology. Most of the existing AOSE methodologies focuses only on analysis, design, implementation and disregarded testing, stating that the testing can be done by extending the existing objectoriented testing techniques. Though objects and agents have some similarities, they both differ widely. Role is an important attribute of an agent that has a huge scope and support for the analysis, design and implementation of Multi-Agent System (MAS). The main objective of the paper is to extend the scope and support of role towards testing, thereby the vacancy for software testing perception in the AOSE series will be filled up. This paper presents an overview of role based testing based on the V-Model in order to add the next new component as of AgentOriented Software testing in the agent oriented development life cycle.

show abstract

Section: B Testing In Aose Methodologiesmentioning

confidence: 99%

Agent Oriented Software Testing – Role Oriented approach

Sivakumar¹,

Vivekanandan²

2012

IJACSA

View full text Add to dashboard Cite

show abstract

“…A categorization for MAS testing from a development-phase activity perspective has been proposed in [28], consisting of five levels: (i) Unit testing targets individual components of an agent, (ii) Agent testing aims at the combination of the components in an agent including capabilities like sensing its environment, (iii) Integration or Group testing includes the communications protocols and the interactions of the agent with its environment or other agents, (iv) System or Society testing considers the expected emergent properties of the system as a whole (v) Acceptance testing for a MAS stays the same as their counterpart in software testing.…”

Section: Levels Of Testingmentioning

confidence: 99%

Seamless Integration and Testing for MAS Engineering

Parizi

Sileno

Engers

2022

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Testing undeniably plays a central role in the daily practice of software engineering, and this explains why better and more efficient libraries and services are continuously made available to developers and designers. Could the MAS developers community similarly benefit from utilizing state-of-the-art testing approaches? The paper investigates the possibility of bringing modern software testing tools as those used in mainstream software engineering into multi-agent systems engineering. Our contribution explores and illustrates, by means of a concrete example, the possible interactions between the agent-based programming framework ASC2 (AgentScript Cross-Compiler) and various testing approaches (unit/agent testing, integration/system testing, continuous integration) and elaborate on how the design choices of ASC2 enable these interactions.

show abstract

“…Five levels of testing a multi-agent system (MAS) are distinguished in [20]: unit, agent, integration, system, and acceptance. In this classification, unit testing targets components that are part of an agent.…”

Section: Related Workmentioning

confidence: 99%

Automating failure detection in cognitive agent programs

Koeman

Hindriks

Jonker

2018

IJAOSE

View full text Add to dashboard Cite

Debugging is notoriously difficult and extremely time consuming but also essential for ensuring the reliability and quality of a software system. In order to reduce debugging effort and enable automated failure detection, we propose an automated testing framework for detecting failures in cognitive agent programs. Our approach is based on the assumption that modules within such programs are a natural unit for testing. We identify a minimal set of temporal operators that enable the specification of test conditions and show that the test language is sufficiently expressive for detecting all failures in an existing failure taxonomy. We also introduce an approach for specifying test templates that supports a programmer in writing tests. Furthermore, empirical analysis of agent programs allows us to evaluate whether our approach using test templates detects all failures.

show abstract

Testing in Agent Oriented Methodologies

Cited by 10 publications

References 12 publications

Agent Oriented Software Testing – Role Oriented approach

Agent Oriented Software Testing – Role Oriented approach

Seamless Integration and Testing for MAS Engineering

Automating failure detection in cognitive agent programs

Contact Info

Product

Resources

About