Flash Source Code Analysis (AS1/AS2)
- or -
Post a project like this£1.5k(approx. $1.8k)
- Posted:
- Proposals: 1
- Remote
- #2114619
- OPPORTUNITY
- Expired
Description
Experience Level: Expert
Estimated project duration: 3 - 4 weeks
Work Description
Working off the QA report, investigate each FLA (AS1/2) to determine what is causing the reported bug. Log observed bug resolution in JIRA for developers to fix. This can be for a fix in the interpreter or the FLA itself. This will often require in-depth tracing to determine exactly what is causing the problem. There may be times a simplified test case is created to confirm the issue.
Workflow Outline
Replicate bug on test. If bug still exists investigation can commence. If bug cannot be replicated or appears fixed, the QA report is updated to Retest and move onto next exercise.
Open up FLA locally and set publish path to local content.
Run local SX2 environment and load exercise.
Begin investigating to identify what is causing the issue. Examples: multiple on events causing none to be triggered. Scoping issues in onEnterFrames...
Once big has been identified, log ticket in JIRA outlining what is causing the problem.
Update QA report - If fix in FLA is required set to Failed FLA, otherwise set to Not Fixed. Add JIRA ticket numbers next to issue(s).
Move onto next exercise.
Working off the QA report, investigate each FLA (AS1/2) to determine what is causing the reported bug. Log observed bug resolution in JIRA for developers to fix. This can be for a fix in the interpreter or the FLA itself. This will often require in-depth tracing to determine exactly what is causing the problem. There may be times a simplified test case is created to confirm the issue.
Workflow Outline
Replicate bug on test. If bug still exists investigation can commence. If bug cannot be replicated or appears fixed, the QA report is updated to Retest and move onto next exercise.
Open up FLA locally and set publish path to local content.
Run local SX2 environment and load exercise.
Begin investigating to identify what is causing the issue. Examples: multiple on events causing none to be triggered. Scoping issues in onEnterFrames...
Once big has been identified, log ticket in JIRA outlining what is causing the problem.
Update QA report - If fix in FLA is required set to Failed FLA, otherwise set to Not Fixed. Add JIRA ticket numbers next to issue(s).
Move onto next exercise.
Bill M.
0% (0)Projects Completed
-
Freelancers worked with
-
Projects awarded
0%
Last project
4 May 2024
United Kingdom
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
Hi Bill, before I put in a bid, could you give an example of a bug report you need looking in to, as well as a brief description of what the software itself is? Both these have a large impact on the time and effort required to debug.
Kind regards,
Will
697743
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies