2010
DOI: 10.1016/j.infsof.2009.06.002
|View full text |Cite
|
Sign up to set email alerts
|

Scalability issues with using FSMWeb to test web applications

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
15
0
2

Year Published

2011
2011
2016
2016

Publication Types

Select...
4
2

Relationship

2
4

Authors

Journals

citations
Cited by 26 publications
(17 citation statements)
references
References 34 publications
0
15
0
2
Order By: Relevance
“…Focus Areas and limitations are shown in given table 8. These identified limitations are complex model [3] [16] [26], annotation cost [6], accuracy [6], lack in tool maturity [10], State space explosion [13], scalability issues [16], error prone [28], time consuming [32], [36], [42], multi components with the same degree [34], performance issues [35], lack of automation [41], quality assurance [41] etc. Focus areas and limitations are shown in given Table 8.…”
Section: Rq3: Which Areas These Approaches Address and What Are The Lmentioning
confidence: 99%
See 2 more Smart Citations
“…Focus Areas and limitations are shown in given table 8. These identified limitations are complex model [3] [16] [26], annotation cost [6], accuracy [6], lack in tool maturity [10], State space explosion [13], scalability issues [16], error prone [28], time consuming [32], [36], [42], multi components with the same degree [34], performance issues [35], lack of automation [41], quality assurance [41] etc. Focus areas and limitations are shown in given Table 8.…”
Section: Rq3: Which Areas These Approaches Address and What Are The Lmentioning
confidence: 99%
“…3) Heterogeneity; that these applications are developed in different programming language (HTML, JavaScript, CSS) for client side and (RUBY, PHP, Java) for server side [13]. 4) Multiple user access.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…Andrews et al [16,17] modeled web applications as hierarchical finite state machines, and generated tests as paths through the FSMs. This approach was pure system level and focused on behavioral aspects of web applications, as opposed to the structural aspects the atomic section model represents.…”
Section: Related Workmentioning
confidence: 99%
“…Further, it also mean that one would need to look deeper into the workload of actual web applications. This process is in its early phases, but there are several examples of interesting work [27,5]. Two concurrent studies [30,31] explicitly compare the JavaScript execution behavior of web applications as compared to existing JavaScript benchmark suites.…”
Section: Related Workmentioning
confidence: 99%