Smalltalk › Pharo › Pharo Smalltalk Users

Applications, features and unit tests

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

4 messages Options

Leonardo Silva

Applications, features and unit tests

Hi everyone,

I am a PhD student at UFMG-Brazil (together with INRIA-France in a project) working with dynamic analysis of software systems' architecture.

The idea, initially, is to check the link between dynamic behavior and static structure (architecture) of a system, regarding its features.

I am looking for real applications in Smalltalk that have a mapping between its features and the specific unit tests for them.

Do you have / know any systems I could use in this research?

The tools I am using are Pharo 3.0 with Roassal (for visualization) and Spy (http://www.smalltalkhub.com/#!/~ObjectProfile/Spy) to capture dynamic behavior.

Many thanks for help,

Leonardo Silva

Marcus Denker-4

Re: Applications, features and unit tests

On 12 Feb 2014, at 13:18, Leonardo Silva <[hidden email]> wrote:

Hi everyone,

I am a PhD student at UFMG-Brazil (together with INRIA-France in a project) working with dynamic analysis of software systems' architecture.

The idea, initially, is to check the link between dynamic behavior and static structure (architecture) of a system, regarding its features.

I am looking for real applications in Smalltalk that have a mapping between its features and the specific unit tests for them.

I once did something that might be related:

Marcus Denker, Jorge Ressia, Orla Greevy, and Oscar Nierstrasz. Modeling Features at Runtime. In Proceedings of MODELS 2010, LNCS 6395 p. 138—152, Springer-Verlag, 2010.

A feature represents a functional requirement fulfilled by a system. Since many maintenance tasks are expressed in terms of features, it is important to establish the correspondence between a feature and its implementation in source code. Traditional approaches to establish this correspondence exercise features to generate a trace of runtime events, which is then processed by post-mortem analysis. These approaches typically generate large amounts of data to analyze. Due to their static nature, these approaches do not support incremental and interactive analysis of features. We propose a radically different approach called live feature analysis, which provides a model at runtime of features. Our approach analyzes features on a running system and also makes it possible to grow feature representations by exercising different scenarios of the same feature, and identifies execution elements even to the sub-method level. We describe how live feature analysis is implemented effectively by annotating structural representations of code based on abstract syntax trees. We illustrate our live analysis with a case study where we achieve a more complete feature representation by exercising and merging variants of feature behavior and demonstrate the efficiency or our technique with benchmarks.

Slides:

http://marcusdenker.de/talks/coauthors/10MODELS/2010-Models-LiveFeatureAnalysis.pdf

Paper:

http://rmod.lille.inria.fr/archives/papers/Denk10a-Models10-FeatureModels.pdf

Damien Cassou

Re: Applications, features and unit tests

In reply to this post by Leonardo Silva

On Wed, Feb 12, 2014 at 1:17 PM, Leonardo Silva
<[hidden email]> wrote:
> I am looking for real applications in Smalltalk that have a mapping between
> its features and the specific unit tests for them.

what is a feature for you? Because, typically, I have a feature per
test. If I need more tests, they typically share the same method name
prefix: e.g., testFeatureNameInSimpleCase,
testFeatureNameInStrangeCase1, testFeatureNameInStrangeCase2...

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm."
Winston Churchill

Leonardo Silva

Re: Applications, features and unit tests

Hi Damien,

By feature I mean any user-visible functionality that needs to be tested. Like you said, one feature can have many tests. The important thing for me is to know, given a unit test, what feature (high level) is going to be tested. If you name your tests putting the name of the feature as a prefix, then I can do this mapping.

Leonardo

On Thu, Feb 13, 2014 at 7:08 AM, Damien Cassou <[hidden email]> wrote:

On Wed, Feb 12, 2014 at 1:17 PM, Leonardo Silva
<[hidden email]> wrote:
> I am looking for real applications in Smalltalk that have a mapping between
> its features and the specific unit tests for them.

what is a feature for you? Because, typically, I have a feature per
test. If I need more tests, they typically share the same method name
prefix: e.g., testFeatureNameInSimpleCase,
testFeatureNameInStrangeCase1, testFeatureNameInStrangeCase2...

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm."
Winston Churchill