Software Agent Testing - FBK | SE - Fondazione Bruno Kessler

More documents

Recommendations

Info

BDI Architecture (recap)n Beliefs: represent the informational state of theagentn Desires: represent the motivational state of theagent¨ Operationalized as Goals + [contextualconditions]n Intentions: represent the deliberative state ofthe agent – what the agent has chosen to do¨ Operationalized as Plansn Events: internal/external triggers that an agentreceives/perceives and will react to.8
<strong>Testing</strong> agent beliefsn Belief state is program state in traditional testingsense:nExample <strong>Agent</strong>: { belief: Bank-Account-Balancegoal: Buy-A-Car }state 1: Bank-Account-Balance = $1,000,0000state 2: Bank-Account-Balance = $100n What to test:¨ Belief update (read/write)n direct: injection, change the agent belief brutallyn indirect: perform belief update via planexecution9
Page 1 and 2: Testing SoftwareAgents & MASCu D. N
Page 3 and 4: Software agents and MASSoftware age
Page 5 and 6: Testing phasesn Acceptance: ensure
Page 7: Some factsn Many BDI agent dev. lan
Page 11 and 12: Testing agent plansn Plans are trig
Page 13 and 14: Example: testing a cleaning agentn
Page 15 and 16: Example (contd.)n Example of goal$b
Page 18 and 19: Ontology-based oraclesn Interaction
Page 20 and 21: Input space in testing agentsn Test
Page 22 and 23: Mock Agentsn Mock Agents are sample
Page 24 and 25: Continuous Testing ofAutonomous Age
Page 26 and 27: Continuous testingn Consists of inp
Page 28 and 29: Random generation• Messages:‣ s
Page 30 and 31: Quality-function-based evolutionary
Page 32 and 33: Example (contd)n Genetic algorithm,
Page 34 and 35: Conclusionsn Testing software agent

Software Agent Testing - FBK | SE - Fondazione Bruno Kessler

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?