Testing Apache FlexJS Applications
summary
Rewrites a legacy Flex app into FlexJS over three months with two half‑time developers, producing about 15–20k lines of code and serving a single codebase across 6 sites to 12 sites with feature toggles; backend uses JSON and AMF, expect millions of users. Build and CI use Maven + Jenkins + GitHub, debugging with Chrome and Charles, quality tracked by SonarQube. Many FlexJS bugs require workarounds but the app is live and functional—FlexJS is roughly 95% production ready.
AI-written summary · about
chapters (39)
- 0:00Intro
- 1:28Who am I?
- 2:51Existing project
- 4:47Community builder
- 8:24Code size
- 10:05One code base many sites
- 12:25What works
- 14:57Risks
- 18:29State of play
- 21:13Unable to set background colours
- 22:23Containers ignore padding
- 24:08Conditional compilation
- 25:44Font support
- 28:02Missing styles
- 30:39Alert is broken
- 31:27Labels are not clickable
- 32:25Background alpha is broken
- 33:15Visibility layout bug
- 35:35Horizontal lists
- 36:12Resizing
- 37:27MXML components
- 37:50Multiline text with newlines
- 38:16Scroll events not dispatched by scroller
- 39:12Visibility changes moves content of container
- 39:59Percent X and Y values
- 40:57Font weight
- 41:18Scroll bars show in browser
- 42:00Observations
- 44:35Things Change
- 46:09Security
- 46:52Back end services
- 49:46Local Development
- 51:25Github
- 51:41Maven
- 52:09Jenkins
- 53:44Hipchat
- 54:36Sonar Cube
- 55:18What next?
- 56:08Questions?
related talks
34mSurviving the Big Rewrite
41mAgile Engineering for Web
26mMaking internets great again - a story of working with legacy code
26mImplementing a test suite in an existing Frontend application
19mSelenium and Flex Pilot
29mFull Stack Scala Web Application.
50mThe State of Server Side Java Webapps
46mFrom Untested Spaghetti to Well-Rested Developers