Suche senden
Hochladen
Static Analysis
•
Als PPT, PDF herunterladen
•
1 gefällt mir
•
503 views
A
alice yang
Folgen
static analysis
Weniger lesen
Mehr lesen
Melden
Teilen
Melden
Teilen
1 von 18
Jetzt herunterladen
Empfohlen
В докладе речь пойдёт о применении алгоритмов машинного обучения для обнаружения вредоносных приложений для Android. Я расскажу, как на базе Матрикснета в Яндексе был спроектирован высокопроизводительный инструмент для решения этой задачи. А также продемонстрирую, в каких случаях аналитические методы выявления вредоносного ПО помогают блокировать множество простых образцов вирусного кода. Затем мы поговорим о том, как можно усовершенствовать такие методы для обнаружения более хитроумных вредных программ.
"Быстрое обнаружение вредоносного ПО для Android с помощью машинного обучения...
"Быстрое обнаружение вредоносного ПО для Android с помощью машинного обучения...
Yandex
Learn how to prevent more Java defects by applying static code analysis, flow analysis, unit testing, and runtime error detection in concert.
Java Defects
Java Defects
Erika Barron
Test Driven Development Thousands of Red-Green-Refactor after…
Tdd Ugialtnet Jan2010
Tdd Ugialtnet Jan2010
guestcff805
Unit Testing
Unit Testing
Ching Yi Chan
A common reason for Null Pointer Exceptions in Java is a variable redeclaration instead of instantiation. Learn what that means, how to avoid it, and how to spot it, in this presentation. Read the full blog post: http://testerhq.com/post/blogs/javafortesters/2017-08-29-faq-null-pointer-exception/ Visit my Java Web Site: http://javafortesters.com --- # FAQ - why does my code throw a null pointer exception - common reason #1 Redeclaration - Using `@BeforeClass` or `@Before` can setup data for use in tests - Any 'variables' we instantiate need to be 'fields' rather than variables - We want to instantiate them in the setup method rather than redeclare them --- # Example of the Problem I know I will use an `Adder` in my test so I create it as a field: ~~~~~~~~ public class WhyCodeThrowsNullPointerExceptionTest { Adder adder; ~~~~~~~~ I don't want to re-instantiate it each time so I make an `@BeforeClass` method to instantiate it: ~~~~~~~~ @BeforeClass public static void setupAdder(){ Adder adder = new Adder(); } ~~~~~~~~ **Warning: Error in the above code** --- # Semantic Error I just made a Semantic coding error. This won't be caught by a compiler, but it will cause my `@Test` to fail with a Null Pointer Exception. In the setup method I really wanted to assign a value to the field, instead I created an new variable with the same name. # In General - Try to write one test at a time so that if you have a problem it is easier to identify where the problem is - Try to write working isolated tests and then refactor to a more general solution when you need it - that way, you know it was working, so you just have to work backwards to find out what went wrong - Try to use automated IDE refactoring rather than move code around manually - Use the IDE syntax highlighting to help spot any issues
FAQ - why does my code throw a null pointer exception - common reason #1 Rede...
FAQ - why does my code throw a null pointer exception - common reason #1 Rede...
Alan Richardson
In this presentation, delivered at Embedded World 2015, we will discuss and compare the ability of unit testing, flow analysis, and static analysis to address software quality, safety, and security issues for embedded systems. In addition to a deep and methodical exploration of how each technology addresses these concerns, we will discuss real-world feedback from organizations that have experience using the technologies in the context of a complete development cycle. The presentation will include the application of unit testing, flow analysis, and static analysis to sample software embedded on an IAR board.
A Comparison of Three Bug-Finding Techniques and Their Relative Effectiveness
A Comparison of Three Bug-Finding Techniques and Their Relative Effectiveness
Parasoft
Learn the strengths and weaknesses of .NET static analysis—and how a comprehensive development testing strategy that also includes unit testing, code review, and runtime error detection can pick up where development testing leaves off.
Beyond Static Analysis: Integrating .NET Static Analysis with Unit Testing a...
Beyond Static Analysis: Integrating .NET Static Analysis with Unit Testing a...
Erika Barron
What would be suitable Code Katas for people wanting to learn how to code to support their testing? CounterStrings - `*3*5*7*9*12*15*` A CounterString is a string like this `*3*5*7*9*12*15*` where the `*` represent the position in the string of the number immediately proceeding it. This is a 15 character CounterString. These are useful because if you paste them into a field, and are truncated then it is easy to see what they were truncated to, it is as James Bach describes it, self documenting test data. https://www.eviltester.com/blog/eviltester/2019-02-27-programming-katas-for-testers/
Programming katas for Software Testers - CounterStrings
Programming katas for Software Testers - CounterStrings
Alan Richardson
Empfohlen
В докладе речь пойдёт о применении алгоритмов машинного обучения для обнаружения вредоносных приложений для Android. Я расскажу, как на базе Матрикснета в Яндексе был спроектирован высокопроизводительный инструмент для решения этой задачи. А также продемонстрирую, в каких случаях аналитические методы выявления вредоносного ПО помогают блокировать множество простых образцов вирусного кода. Затем мы поговорим о том, как можно усовершенствовать такие методы для обнаружения более хитроумных вредных программ.
"Быстрое обнаружение вредоносного ПО для Android с помощью машинного обучения...
"Быстрое обнаружение вредоносного ПО для Android с помощью машинного обучения...
Yandex
Learn how to prevent more Java defects by applying static code analysis, flow analysis, unit testing, and runtime error detection in concert.
Java Defects
Java Defects
Erika Barron
Test Driven Development Thousands of Red-Green-Refactor after…
Tdd Ugialtnet Jan2010
Tdd Ugialtnet Jan2010
guestcff805
Unit Testing
Unit Testing
Ching Yi Chan
A common reason for Null Pointer Exceptions in Java is a variable redeclaration instead of instantiation. Learn what that means, how to avoid it, and how to spot it, in this presentation. Read the full blog post: http://testerhq.com/post/blogs/javafortesters/2017-08-29-faq-null-pointer-exception/ Visit my Java Web Site: http://javafortesters.com --- # FAQ - why does my code throw a null pointer exception - common reason #1 Redeclaration - Using `@BeforeClass` or `@Before` can setup data for use in tests - Any 'variables' we instantiate need to be 'fields' rather than variables - We want to instantiate them in the setup method rather than redeclare them --- # Example of the Problem I know I will use an `Adder` in my test so I create it as a field: ~~~~~~~~ public class WhyCodeThrowsNullPointerExceptionTest { Adder adder; ~~~~~~~~ I don't want to re-instantiate it each time so I make an `@BeforeClass` method to instantiate it: ~~~~~~~~ @BeforeClass public static void setupAdder(){ Adder adder = new Adder(); } ~~~~~~~~ **Warning: Error in the above code** --- # Semantic Error I just made a Semantic coding error. This won't be caught by a compiler, but it will cause my `@Test` to fail with a Null Pointer Exception. In the setup method I really wanted to assign a value to the field, instead I created an new variable with the same name. # In General - Try to write one test at a time so that if you have a problem it is easier to identify where the problem is - Try to write working isolated tests and then refactor to a more general solution when you need it - that way, you know it was working, so you just have to work backwards to find out what went wrong - Try to use automated IDE refactoring rather than move code around manually - Use the IDE syntax highlighting to help spot any issues
FAQ - why does my code throw a null pointer exception - common reason #1 Rede...
FAQ - why does my code throw a null pointer exception - common reason #1 Rede...
Alan Richardson
In this presentation, delivered at Embedded World 2015, we will discuss and compare the ability of unit testing, flow analysis, and static analysis to address software quality, safety, and security issues for embedded systems. In addition to a deep and methodical exploration of how each technology addresses these concerns, we will discuss real-world feedback from organizations that have experience using the technologies in the context of a complete development cycle. The presentation will include the application of unit testing, flow analysis, and static analysis to sample software embedded on an IAR board.
A Comparison of Three Bug-Finding Techniques and Their Relative Effectiveness
A Comparison of Three Bug-Finding Techniques and Their Relative Effectiveness
Parasoft
Learn the strengths and weaknesses of .NET static analysis—and how a comprehensive development testing strategy that also includes unit testing, code review, and runtime error detection can pick up where development testing leaves off.
Beyond Static Analysis: Integrating .NET Static Analysis with Unit Testing a...
Beyond Static Analysis: Integrating .NET Static Analysis with Unit Testing a...
Erika Barron
What would be suitable Code Katas for people wanting to learn how to code to support their testing? CounterStrings - `*3*5*7*9*12*15*` A CounterString is a string like this `*3*5*7*9*12*15*` where the `*` represent the position in the string of the number immediately proceeding it. This is a 15 character CounterString. These are useful because if you paste them into a field, and are truncated then it is easy to see what they were truncated to, it is as James Bach describes it, self documenting test data. https://www.eviltester.com/blog/eviltester/2019-02-27-programming-katas-for-testers/
Programming katas for Software Testers - CounterStrings
Programming katas for Software Testers - CounterStrings
Alan Richardson
Everyone says you should test your designs, but expects you to know what that testing should be. Here we briefly look at the kinds of tests (software) engineers might encounter and what the terms being used actually mean. Finally we settle on Unit Testing as a good place to begin the testing process.
Unit testing
Unit testing
jeslie
Interaction testing using mock objects
Interaction testing using mock objects
Lim Chanmann
It's very interesting to check large projects. As a rule, we do manage to find unusual and peculiar errors, and tell people about them. Also, it's a great way to test our analyzer and improve all its different aspects. I've long been waiting to check 'Mono'; and finally, I got the opportunity. I should say that this check really proved its worth as I was able to find a lot of entertaining things. This article is about the bugs we found, and several nuances which arose during the check.
Searching for bugs in Mono: there are hundreds of them!
Searching for bugs in Mono: there are hundreds of them!
PVS-Studio
Learn the strengths and weaknesses of Java static analysis—and how a comprehensive development testing strategy that also includes unit testing, code review, and runtime error detection can pick up where development testing leaves off.
Beyond Static Analysis: Integrating Java Static Analysis with Unit Testing an...
Beyond Static Analysis: Integrating Java Static Analysis with Unit Testing an...
Erika Barron
Extreme. ESUG 2007, Lugano
Extreme
Extreme
ESUG
In this presentation I talked about Secure Software Development Life Cycle Design Issues. Threat Modeling. Static Code Analysis. Pentesting. Resources.
Security for developers
Security for developers
Abdelrhman Shawky
Despite various debugging supports of the existing IDEs for programming errors and exceptions, software developers often look at web for working solutions or any up-to-date information. Traditional web search does not consider thecontext of the problems that they search solutions for, and thus it often does not help much in problem solving. In this paper, we propose a context-aware meta search tool, SurfClipse, that analyzes an encountered exception andits context in the IDE, and recommends not only suitable search queries but also relevant web pages for the exception (and its context). The tool collects results from three popular search engines and a programming Q & A site against the exception in the IDE, refines the results for relevance against the context of the exception, and then ranks them before recommendation. It provides two working modes--interactive and proactive to meet the versatile needs of the developers, and one can browse the result pages using a customized embedded browser provided by the tool.
SurfClipse-- An IDE based context-aware Meta Search Engine
SurfClipse-- An IDE based context-aware Meta Search Engine
Masud Rahman
it camp
Mocking
Mocking
eleksdev
Integration testing
Integration testing
Integration testing
Tsegabrehan Am
NASA interns exploring the REACTIS tool
Reactis
Reactis
CS, NcState
Parasoft .TEST, Write better C# Code Using Data Flow Analysis
Parasoft .TEST, Write better C# Code Using Data Flow Analysis
Parasoft .TEST, Write better C# Code Using Data Flow Analysis
Engineering Software Lab
Software Testing (Basics + Manual + Automated)
Software testing
Software testing
Enamul Haque
Several static analysis tools, such as Splint or FindBugs, have been proposed to the software development community to help detect security vulnerabilities or bad programming practices. However, the adoption of these tools is hindered by their high false positive rates. If the false positive rate is too high, developers may get acclimated to violation reports from these tools, causing concrete and severe bugs being overlooked. Fortunately, some violations are actually addressed and resolved by developers. We claim that those violations that are recurrently fixed are likely to be true positives, and an automated approach can learn to repair similar unseen violations. However, there is lack of a systematic way to investigate the distributions on existing violations and fixed ones in the wild, that can provide insights into prioritizing violations for developers, and an effective way to mine code and fix patterns which can help developers easily understand the reasons of leading violations and how to fix them. In this paper, we first collect and track a large number of fixed and unfixed violations across revisions of software. The empirical analyses reveal that there are discrepancies in the distributions of violations that are detected and those that are fixed, in terms of occurrences, spread and categories, which can provide insights into prioritizing violations. To automatically identify patterns in violations and their fixes, we propose an approach that utilizes convolutional neural networks to learn features and clustering to regroup similar instances. We then evaluate the usefulness of the identified fix patterns by applying them to unfixed violations. The results show that developers will accept and merge a majority (69/116) of fixes generated from the inferred fix patterns. It is also noteworthy that the yielded patterns are applicable to four real bugs in the Defects4J major benchmark for software testing and automated repair.
Mining Fix Patterns for FindBugs Violations
Mining Fix Patterns for FindBugs Violations
Dongsun Kim
JavaOne presentation looking at the different tools available to JavaScript developers for debugging, performance and deployment
Pragmatic Parallels: Java and JavaScript
Pragmatic Parallels: Java and JavaScript
davejohnson
What is testing? What is agile testing? What is automated testing? What is agile testing? Unit testing Mock testing Functional testing Acceptance testing Integration testing Performance/load/stress testing Deployment testing Methods of testing White/black/grayboxtesting GUI vs. businesslogictesting Improving code testability Codefacing vs. businessfacingtesting Smoke testing Automated testing strategies Virtualization Code coverage Resources File Can be downloaded from: http://community.scmgalaxy.com/
Testing in a glance
Testing in a glance
Rajesh Kumar
Introduction to automated quality assurance
Introduction to automated quality assurance
Philip Johnson
An important event has taken place in the PVS-Studio analyzer's life: support of C#-code analysis was added in the latest version. As one of its developers, I couldn't but try it on some project. Reading about scanning small and little-known projects is not much interesting of course, so it had to be something popular, and I picked MonoDevelop.
Looking for Bugs in MonoDevelop
Looking for Bugs in MonoDevelop
PVS-Studio
Talk at FUM. Oct 2015. Directed Model Inference for Testing and Analysis of Web Applications
Amin Milani Fard: Directed Model Inference for Testing and Analysis of Web Ap...
Amin Milani Fard: Directed Model Inference for Testing and Analysis of Web Ap...
knowdiff
Presentation at Oracle Code 2018 in San Francisco showing how to create a test architecture for web automation
Create an architecture for web test automation
Create an architecture for web test automation
Elias Nogueira
How to approach testing if you are building a modern single page application. I try to emphasize that integration testing is the way to go and that developers should consider the tests as part of the system and spend time to maintain them.
Writing useful automated tests for the single page applications you build
Writing useful automated tests for the single page applications you build
Andrei Sebastian Cîmpean
Agile Testing Pasadena JUG Aug2009
Agile Testing Pasadena JUG Aug2009
Grig Gheorghiu
A brief introduction to software unit testing.
Unit testing - An introduction
Unit testing - An introduction
Alejandro Claro Mosqueda
Weitere ähnliche Inhalte
Was ist angesagt?
Everyone says you should test your designs, but expects you to know what that testing should be. Here we briefly look at the kinds of tests (software) engineers might encounter and what the terms being used actually mean. Finally we settle on Unit Testing as a good place to begin the testing process.
Unit testing
Unit testing
jeslie
Interaction testing using mock objects
Interaction testing using mock objects
Lim Chanmann
It's very interesting to check large projects. As a rule, we do manage to find unusual and peculiar errors, and tell people about them. Also, it's a great way to test our analyzer and improve all its different aspects. I've long been waiting to check 'Mono'; and finally, I got the opportunity. I should say that this check really proved its worth as I was able to find a lot of entertaining things. This article is about the bugs we found, and several nuances which arose during the check.
Searching for bugs in Mono: there are hundreds of them!
Searching for bugs in Mono: there are hundreds of them!
PVS-Studio
Learn the strengths and weaknesses of Java static analysis—and how a comprehensive development testing strategy that also includes unit testing, code review, and runtime error detection can pick up where development testing leaves off.
Beyond Static Analysis: Integrating Java Static Analysis with Unit Testing an...
Beyond Static Analysis: Integrating Java Static Analysis with Unit Testing an...
Erika Barron
Extreme. ESUG 2007, Lugano
Extreme
Extreme
ESUG
In this presentation I talked about Secure Software Development Life Cycle Design Issues. Threat Modeling. Static Code Analysis. Pentesting. Resources.
Security for developers
Security for developers
Abdelrhman Shawky
Despite various debugging supports of the existing IDEs for programming errors and exceptions, software developers often look at web for working solutions or any up-to-date information. Traditional web search does not consider thecontext of the problems that they search solutions for, and thus it often does not help much in problem solving. In this paper, we propose a context-aware meta search tool, SurfClipse, that analyzes an encountered exception andits context in the IDE, and recommends not only suitable search queries but also relevant web pages for the exception (and its context). The tool collects results from three popular search engines and a programming Q & A site against the exception in the IDE, refines the results for relevance against the context of the exception, and then ranks them before recommendation. It provides two working modes--interactive and proactive to meet the versatile needs of the developers, and one can browse the result pages using a customized embedded browser provided by the tool.
SurfClipse-- An IDE based context-aware Meta Search Engine
SurfClipse-- An IDE based context-aware Meta Search Engine
Masud Rahman
it camp
Mocking
Mocking
eleksdev
Integration testing
Integration testing
Integration testing
Tsegabrehan Am
NASA interns exploring the REACTIS tool
Reactis
Reactis
CS, NcState
Was ist angesagt?
(10)
Unit testing
Unit testing
Interaction testing using mock objects
Interaction testing using mock objects
Searching for bugs in Mono: there are hundreds of them!
Searching for bugs in Mono: there are hundreds of them!
Beyond Static Analysis: Integrating Java Static Analysis with Unit Testing an...
Beyond Static Analysis: Integrating Java Static Analysis with Unit Testing an...
Extreme
Extreme
Security for developers
Security for developers
SurfClipse-- An IDE based context-aware Meta Search Engine
SurfClipse-- An IDE based context-aware Meta Search Engine
Mocking
Mocking
Integration testing
Integration testing
Reactis
Reactis
Ähnlich wie Static Analysis
Parasoft .TEST, Write better C# Code Using Data Flow Analysis
Parasoft .TEST, Write better C# Code Using Data Flow Analysis
Parasoft .TEST, Write better C# Code Using Data Flow Analysis
Engineering Software Lab
Software Testing (Basics + Manual + Automated)
Software testing
Software testing
Enamul Haque
Several static analysis tools, such as Splint or FindBugs, have been proposed to the software development community to help detect security vulnerabilities or bad programming practices. However, the adoption of these tools is hindered by their high false positive rates. If the false positive rate is too high, developers may get acclimated to violation reports from these tools, causing concrete and severe bugs being overlooked. Fortunately, some violations are actually addressed and resolved by developers. We claim that those violations that are recurrently fixed are likely to be true positives, and an automated approach can learn to repair similar unseen violations. However, there is lack of a systematic way to investigate the distributions on existing violations and fixed ones in the wild, that can provide insights into prioritizing violations for developers, and an effective way to mine code and fix patterns which can help developers easily understand the reasons of leading violations and how to fix them. In this paper, we first collect and track a large number of fixed and unfixed violations across revisions of software. The empirical analyses reveal that there are discrepancies in the distributions of violations that are detected and those that are fixed, in terms of occurrences, spread and categories, which can provide insights into prioritizing violations. To automatically identify patterns in violations and their fixes, we propose an approach that utilizes convolutional neural networks to learn features and clustering to regroup similar instances. We then evaluate the usefulness of the identified fix patterns by applying them to unfixed violations. The results show that developers will accept and merge a majority (69/116) of fixes generated from the inferred fix patterns. It is also noteworthy that the yielded patterns are applicable to four real bugs in the Defects4J major benchmark for software testing and automated repair.
Mining Fix Patterns for FindBugs Violations
Mining Fix Patterns for FindBugs Violations
Dongsun Kim
JavaOne presentation looking at the different tools available to JavaScript developers for debugging, performance and deployment
Pragmatic Parallels: Java and JavaScript
Pragmatic Parallels: Java and JavaScript
davejohnson
What is testing? What is agile testing? What is automated testing? What is agile testing? Unit testing Mock testing Functional testing Acceptance testing Integration testing Performance/load/stress testing Deployment testing Methods of testing White/black/grayboxtesting GUI vs. businesslogictesting Improving code testability Codefacing vs. businessfacingtesting Smoke testing Automated testing strategies Virtualization Code coverage Resources File Can be downloaded from: http://community.scmgalaxy.com/
Testing in a glance
Testing in a glance
Rajesh Kumar
Introduction to automated quality assurance
Introduction to automated quality assurance
Philip Johnson
An important event has taken place in the PVS-Studio analyzer's life: support of C#-code analysis was added in the latest version. As one of its developers, I couldn't but try it on some project. Reading about scanning small and little-known projects is not much interesting of course, so it had to be something popular, and I picked MonoDevelop.
Looking for Bugs in MonoDevelop
Looking for Bugs in MonoDevelop
PVS-Studio
Talk at FUM. Oct 2015. Directed Model Inference for Testing and Analysis of Web Applications
Amin Milani Fard: Directed Model Inference for Testing and Analysis of Web Ap...
Amin Milani Fard: Directed Model Inference for Testing and Analysis of Web Ap...
knowdiff
Presentation at Oracle Code 2018 in San Francisco showing how to create a test architecture for web automation
Create an architecture for web test automation
Create an architecture for web test automation
Elias Nogueira
How to approach testing if you are building a modern single page application. I try to emphasize that integration testing is the way to go and that developers should consider the tests as part of the system and spend time to maintain them.
Writing useful automated tests for the single page applications you build
Writing useful automated tests for the single page applications you build
Andrei Sebastian Cîmpean
Agile Testing Pasadena JUG Aug2009
Agile Testing Pasadena JUG Aug2009
Grig Gheorghiu
A brief introduction to software unit testing.
Unit testing - An introduction
Unit testing - An introduction
Alejandro Claro Mosqueda
B2 2005 introduction_load_testing_blackboard_primer_draft
B2 2005 introduction_load_testing_blackboard_primer_draft
Steve Feldman
The field of machine programming — the automation of the development of software — is making notable research advances. This is, in part, due to the emergence of a wide range of novel techniques in machine learning. In today’s technological landscape, software is integrated into almost everything we do, but maintaining software is a time-consuming and error-prone process. When fully realized, machine programming will enable everyone to express their creativity and develop their own software without writing a single line of code. Intel realizes the pioneering promise of machine programming, which is why it created the Machine Programming Research (MPR) team in Intel Labs. The MPR team’s goal is to create a society where everyone can create software, but machines will handle the “programming” part.
Machine programming
Machine programming
DESMOND YUEN
Yazid Boutejder: AWS San Francisco Startup Day, 9/7/17 Operations: Production Readiness Review – how to stop bad things from happening - There is more to deploying code than pushing the deploy button. A good practice that many companies follow is a Production Readiness Review (PRR) which is essentially a pre-flight check list before a service launches. This helps ensure new services are properly architected, monitored, secured, and more. We’ll walk through an example PRR and discuss the value of ensuring each of these is properly taken care of before your service launches.
Operations: Production Readiness
Operations: Production Readiness
Amazon Web Services
Static code analysis
Static code analysis
Rune Sundling
1st DSV-PhD Workshop: Keynote speech by Marcus Lagergren, Oracle Inc.
Lessons Learned in Software Development: QA Infrastructure – Maintaining Rob...
Lessons Learned in Software Development: QA Infrastructure – Maintaining Rob...
Cωνσtantίnoς Giannoulis
Presentation given during Startup Day in Austin on August 3, 2017 within the Operations track
Start Up Austin 2017: Production Preview - How to Stop Bad Things From Happening
Start Up Austin 2017: Production Preview - How to Stop Bad Things From Happening
Amazon Web Services
Presentation from Progressive.NET 2012 workshop on Testing ASP.NET web applications.
Testing ASP.NET - Progressive.NET
Testing ASP.NET - Progressive.NET
Ben Hall
10 Ways To Improve Your Code
10 Ways To Improve Your Code
ConSanFrancisco123
Ähnlich wie Static Analysis
(20)
Parasoft .TEST, Write better C# Code Using Data Flow Analysis
Parasoft .TEST, Write better C# Code Using Data Flow Analysis
Software testing
Software testing
Mining Fix Patterns for FindBugs Violations
Mining Fix Patterns for FindBugs Violations
Pragmatic Parallels: Java and JavaScript
Pragmatic Parallels: Java and JavaScript
Testing in a glance
Testing in a glance
Introduction to automated quality assurance
Introduction to automated quality assurance
Looking for Bugs in MonoDevelop
Looking for Bugs in MonoDevelop
Amin Milani Fard: Directed Model Inference for Testing and Analysis of Web Ap...
Amin Milani Fard: Directed Model Inference for Testing and Analysis of Web Ap...
Create an architecture for web test automation
Create an architecture for web test automation
Writing useful automated tests for the single page applications you build
Writing useful automated tests for the single page applications you build
Agile Testing Pasadena JUG Aug2009
Agile Testing Pasadena JUG Aug2009
Unit testing - An introduction
Unit testing - An introduction
B2 2005 introduction_load_testing_blackboard_primer_draft
B2 2005 introduction_load_testing_blackboard_primer_draft
Machine programming
Machine programming
Operations: Production Readiness
Operations: Production Readiness
Static code analysis
Static code analysis
Lessons Learned in Software Development: QA Infrastructure – Maintaining Rob...
Lessons Learned in Software Development: QA Infrastructure – Maintaining Rob...
Start Up Austin 2017: Production Preview - How to Stop Bad Things From Happening
Start Up Austin 2017: Production Preview - How to Stop Bad Things From Happening
Testing ASP.NET - Progressive.NET
Testing ASP.NET - Progressive.NET
10 Ways To Improve Your Code
10 Ways To Improve Your Code
Static Analysis
1.
Improve SAKS.com
Software Quality through Static Analysis Even before Testing
2.
Comparison of costs
to fix defects at different stages
3.
4.
5.
6.
7.
8.
9.
Bug Categories
10.
Bug Categories
11.
How to use
FindBugs
12.
Bugs Detection Process
13.
FindBugs Analysis Report
14.
15.
High Light Issues—checkout.js
16.
17.
18.
Jetzt herunterladen